Home

Issues with WS-FED Sign In

%3CLINGO-SUB%20id%3D%22lingo-sub-85556%22%20slang%3D%22en-US%22%3EIssues%20with%20WS-FED%20Sign%20In%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-85556%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20having%20issues%20getting%20WS-FED%20SSO%20working%20between%20our%20ID%20provider%20solution%20(ForgeRock%20Identity)%20and%20the%20O365%20platform.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20succesfully%20configured%20O365%20with%20our%20ForgeRock%20domain%20and%20set%20it%20as%20a%20federated%20sign%20in.%20I%20have%20added%20a%20test%20user%20to%20the%20O365%2FAzureAD%20and%20have%20an%20equivalent%20user%20in%20our%20ID%20platform%2C%20with%20identical%20UPN%20and%20GUID%20values.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20also%20set%20the%20WS-FED%20claims%20to%20send%20GUID%20as%20the%20'immutable%20value'%20and%20the%20the%20UPN%20as%20name-ID.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%20when%20we%20try%20a%20federated%20sign%20in%2C%20we%20get%20the%20below%20error%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3ECorrelation%20ID%3A%2097a24147-748f-458b-9c4c-4c2eca9df121%0ATimestamp%3A%202017-07-07%2010%3A24%3A26Z%0AAADSTS51004%3A%20To%20sign%20into%20this%20application%20the%20account%203e95c26f-6759-4dcf-81b5-2fe6f727622b%20must%20be%20added%20to%20the%20661d88d5-4341-4f09-b435-e5c92c5ad753%20directory.%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20checked%20the%20test%20user%20and%20the%20user%20GUID%20(3e95c26f-6759-4dcf-81b5-2fe6f727622b)%20detailed%20in%20the%20error%20message%20is%20correct%20and%20that%20user%20is%20in%20the%20AzureAD%20directory%20(661d88d5-4341-4f09-b435-e5c92c5ad753)%20so%20I%20am%20not%20sure%20why%20we%20are%20getting%20this%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20anyone%20help%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-85556%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAccess%20Management%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20AD%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIdentity%20Management%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-86029%22%20slang%3D%22en-US%22%3ERe%3A%20Issues%20with%20WS-FED%20Sign%20In%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-86029%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Andrew%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20no%20personal%20experience%20with%20ForgeRock%2C%20but%20it%20would%20be%20up%20to%20the%20IDM%20to%20provide%20support%20for%20Azure%2FO365%20connectivity.%20So%20basically%2C%20if%20ForgeRock%20says%20it%20needs%20the%20connector%2C%20then%20it%20does.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-85970%22%20slang%3D%22en-US%22%3ERe%3A%20Issues%20with%20WS-FED%20Sign%20In%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-85970%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Jeff.%20Thanks%20for%20the%20reply.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20aware%20ForgeRock%20is%20not%20'officially'%20supported%2C%20but%20given%20that%20WS-Fed%20is%20a%20standard%20that%20our%20FR%20platform%20can%20use%2C%20I%20am%20hoping%20we%20can%20get%20it%20working%20anyway!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%20I%20don't%20have%20access%20to%20stash.forgerock.org%20so%20I%20cannot%20see%20the%20details%2C%20however%20would%20I%20be%20correct%20in%20assuming%20that%20the%20IDM%20%26gt%3B%20AzureAD%20connector%20mentioned%20in%20that%20thread%20would%20be%20required%20to%20allow%20user%20provisioning%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20do%20not%20want%20to%20enable%20provisioning.%20We%20simply%20want%20to%20do%20SSO%20authentication.%20Do%20you%20know%20if%20this%20connector%20is%20still%20required%20for%20this%20use%20case%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-85667%22%20slang%3D%22en-US%22%3ERe%3A%20Issues%20with%20WS-FED%20Sign%20In%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-85667%22%20slang%3D%22en-US%22%3E%3CP%3EForgeRock%20Identity%20is%20not%20on%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fconnect%2Factive-directory-aadconnect-federation-compatibility%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20AD%20federation%20compatibility%20list%3C%2FA%3E%2C%20so%20it%20has%20not%20been%20validated%20to%20work%20with%20Office%20365.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20said%2C%20you%20can%20try%20following%20this%20%3CA%20href%3D%22https%3A%2F%2Fforum.forgerock.com%2Ftopic%2Fopenidm-and-office-365-integration%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EForgeRock%20OpenIDM%20and%20Office%20365%3C%2FA%3E%20post%2C%20which%20links%20to%20scripts%20they%20are%20developing%20for%20integration.%20Keep%20in%20mind%2C%20it's%20a%20work%20in%20progress%20and%20is%20only%20supported%20by%20ForgeRock.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Andrew Firth
New Contributor

Hello,

 

I am having issues getting WS-FED SSO working between our ID provider solution (ForgeRock Identity) and the O365 platform.

 

I have succesfully configured O365 with our ForgeRock domain and set it as a federated sign in. I have added a test user to the O365/AzureAD and have an equivalent user in our ID platform, with identical UPN and GUID values.

 

I have also set the WS-FED claims to send GUID as the 'immutable value' and the the UPN as name-ID.

 

However when we try a federated sign in, we get the below error:

 

Correlation ID: 97a24147-748f-458b-9c4c-4c2eca9df121
Timestamp: 2017-07-07 10:24:26Z
AADSTS51004: To sign into this application the account 3e95c26f-6759-4dcf-81b5-2fe6f727622b must be added to the 661d88d5-4341-4f09-b435-e5c92c5ad753 directory.

 

I have checked the test user and the user GUID (3e95c26f-6759-4dcf-81b5-2fe6f727622b) detailed in the error message is correct and that user is in the AzureAD directory (661d88d5-4341-4f09-b435-e5c92c5ad753) so I am not sure why we are getting this error.

 

Can anyone help?

 

3 Replies

ForgeRock Identity is not on the Azure AD federation compatibility list, so it has not been validated to work with Office 365.

 

That said, you can try following this ForgeRock OpenIDM and Office 365 post, which links to scripts they are developing for integration. Keep in mind, it's a work in progress and is only supported by ForgeRock.

Hi Jeff. Thanks for the reply.

 

I am aware ForgeRock is not 'officially' supported, but given that WS-Fed is a standard that our FR platform can use, I am hoping we can get it working anyway!

 

Unfortunately I don't have access to stash.forgerock.org so I cannot see the details, however would I be correct in assuming that the IDM > AzureAD connector mentioned in that thread would be required to allow user provisioning?

 

We do not want to enable provisioning. We simply want to do SSO authentication. Do you know if this connector is still required for this use case?

Hi Andrew,

 

I have no personal experience with ForgeRock, but it would be up to the IDM to provide support for Azure/O365 connectivity. So basically, if ForgeRock says it needs the connector, then it does.

 

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
35 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies