JeffM.43402 (Customer) asked a question.
Custom Application Username Causes Internal System Error
I apologize for making this a "question" instead of a support request -- but the support request feature was giving me an "internal error". So...go figure. I have (two now) applications that I want to use `${user.employeeNumber}` as the SAML "Application username" and when it is set up as such I can't add any users to the application. When I add the 'everyone' group the login process fails, telling me I'm not authorized 🙂 When I attempt to add the user to the application(s) from the user's profile page, I get a 500 error response, one example of the return content is:
- {"errorCode":"E0000009","errorSummary":"Internal Server Error","errorLink":"E0000009","errorId":"oae_s0ehfWVTPeP7tOOzAMHpw","errorCauses":[]}
- If you go to Director->Profile Editor-Profiles Mappings
- Select the Mapping for the Apps in question
- Select the 'Okta to App in question'
- Override the username mapping and define
- user.employeeNumber maps to app.userName (or user.employeeID != null ? source.employeeID : 000000)
- select the appropriate 1 time or all time mapping
- Select 'Save Mappings'
- If you have the mapping set to apply mapping on user create and update you can select the option to Apply updates now to update the username for existing application assginments.
If you are already setting it up this way and getting those errors i'm at a loss.-Matt