<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D51Y00009L9QlBSAVOkta Classic EngineOkta Integration NetworkAnswered2022-06-07T11:15:50.000Z2020-09-04T12:21:37.000Z2020-09-11T14:00:47.000Z
Username format is showing as blank after user assigned to the application, however the value still passing in SAML assertion.

Hello guys,

 

We recently migrated O365 application to OKTA and we are seeing issue with username format for some users. Even though user has valid GUID value and properly mapped the profile attribute. After user assigned to the application the Immutable ID field showing as blank, But I can see in the SAML tracer that Immutable ID is passing in SAML assertion .

 

If any one gone through similar situation . Kindly let me know why the field showing as blank and how it got resolved.

 

Thanks

 


  • User15871004093001868702 (Vendor Management)

    Okta Office 365 User Management will fail if the ImmutableId value in Okta doesn't match what has been set in Office 365. There are a couple of ways this can happen. In order to fix it, you need to set the ImmutableId in office 365 to the correct value. If the User is an AD user, the ImmutableID is set to AD GUID. If the user is an Okta Only User, the immutable ID is set to the application assignment ID.

     If the issue still persist i will recommend to open a case with support and also check both the logs in Okta and on Office 365.

    Expand Post
This question is closed.
Loading
Username format is showing as blank after user assigned to the application, however the value still passing in SAML assertion.