Apex Code Development You need to sign in to do that
Don't have an account?
Jonathan Schmalzle 2 Custom JIT Handler with Encrypted Assertion
We are implementing a Custom Apex JIT Handler for a Single Sign On Configuration. The JIT Handler is invoked by the system using the following methods:
- global User createUser(Id samlSsoProviderId, Id communityId, Id portalId, String federationIdentifier, Map<String, String> attributes, String assertion)
- global void updateUser(Id userId, Id samlSsoProviderId, Id communityId, Id portalId, String federationIdentifier, Map<String, String> attributes, String assertion)
When the assertion is not encrypted we get all of the parameters passed in to these methods. When the assertion is encrypted everything is passed in but the attributes parameter is empty.
Has anyone experienced this issue?
- global User createUser(Id samlSsoProviderId, Id communityId, Id portalId, String federationIdentifier, Map<String, String> attributes, String assertion)
- global void updateUser(Id userId, Id samlSsoProviderId, Id communityId, Id portalId, String federationIdentifier, Map<String, String> attributes, String assertion)
When the assertion is not encrypted we get all of the parameters passed in to these methods. When the assertion is encrypted everything is passed in but the attributes parameter is empty.
Has anyone experienced this issue?
I have implemented the Standard JIT provisioning and the issue i am running into is : If the user already exists, then the system still tries update his profile with hard coded value(Big issue for admins)
Question: Was this the reason that you had to implement the Custsom JIt class?