Hey All,
I have built a SCIM server using AWS API gateway backed by a Lambda function.
So when a user is assigned to my app in okta, it triggers a GET request followed by a POST request which handles user creation.
But when i change any attribute of a user in okta, it shows PROFILE PUSH FOR USER FAILED, NO USER FOUND. How is this being done? it doesnt trigger the lambda function at all.
Sample POST request :
"
‘http’: {‘method’: ‘POST’, ‘path’: ‘/Scim/v2/Users’, ‘protocol’: ‘HTTP/1.1’, ‘sourceIp’: ‘54.71.214.179’, ‘userAgent’: ‘Okta SCIM Client 1.0.0’}, ‘requestId’: ‘CowgCh8QoAMESgQ=’, ‘routeKey’: ‘POST /Scim/v2/Users’, ‘stage’: ‘$default’, ‘time’: ‘11/Dec/2024:17:10:49 +0000’, ‘timeEpoch’: 1733937049497}, ‘body’: ‘{“schemas”:[“urn:ietf:params:scim:schemas:core:2.0:User”],“userName”:“test@gmail”,“name”:{“givenName”:“test@gmail”,“familyName”:“test@gmail”},“emails”:[{“primary”:true,“value”:“test@gmail”,“type”:“work”}],“locale”:“en-US”,“externalId”:“00ulsk8yrfq1LNH5o5d7”,“groups”:,“password”:“yM8mUZ3J”,“active”:true}’, ‘isBase64Encoded’: False}
"
respective response from my endpoint :
"
SCIM response: {‘statusCode’: 201, ‘body’: ‘{“schemas”: [“urn:ietf:params:scim:schemas:core:2.0:User”], “id”: “test@gmail”, “userName”: “test@gmail”, “emails”: [{“value”: “test@gmail”, “primary”: true, “type”: “work”}], “active”: true}’, ‘headers’: {‘Content-Type’: ‘application/scim+json’}}
"
anytime i update any of the attributes it shows : "
Automatic profile push of user p b to app ToxMod - Cloud Env failed: Error while trying to push profile update for test@gmail: No user returned for user test@gmail
"