<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
0D51Y000091isxnSAAOkta Classic EngineIntegrationsUnanswered2020-08-19T12:50:09.000Z2020-08-19T12:50:09.000Z

CorneV.55073 (Customer) asked a question.

Atlassian Cloud OIN app fails to provision users, missing "primary email"

Hallo folks,

 

has anyone had success in using the OIN app for Atlassian Cloud, specifically to provision users to the Atlassian Access product? We have an issue where provisioning complains that it's missing the required field "primary email", although it is non-empty.

 

We use Namely as the profile master - the "email" attribute is correctly mapped from Namely into Okta UD and can be verified as having the correct value in a preview.

 

When inspecting the user profiles after API integration was enabled for the Atlassian app, the "email " attribute is empty though, but it isn't clear why this should be the case, as it has the correct value everywhere else.

 

Anyone come across something similar?

 

regards

Corne


This question is closed.
Loading
Atlassian Cloud OIN app fails to provision users, missing "primary email"