This message was deleted.
# citrix-netscalers
Slackbot
01/20/2021, 12:10 PMThis message was deleted.
f
Frank Vandebergh
01/20/2021, 12:25 PMYou would have to register the application first as if it is within a specific tenant, and then change the endpoint urls to use the common instead of tenantid.
In Azure AD the app will be in enterprise applications but also be in ‘app registrations’ where you configure the client secret. the client id will be the Application ID when you view the app registration.
k
Kari Ruissalo (WyW)
01/20/2021, 12:32 PMreally? that simple... I'll give it a go immediately 🙂
Kari Ruissalo (WyW)
01/20/2021, 12:51 PMI did this (really quick test), in the Enterprise App the SSO bit guides to go to "App Registrations".
... I went there and created a Client Secret and added that value in to the ADC config. Now I'm getting "Invalid State value presented" on ADC.
I have configured following:
Client ID = Enterprise App, Application ID
Client Secret = App Registration, Client Secret Value
Authz EP = https://login.microsoftonline.com/common/oauth2/v2.0/authorize
Token EP = https://login.microsoftonline.com/common/oauth2/v2.0/token
Graph EP = https://graph.microsoft.com/oidc/userinfo
Cert EP = https://login.microsoftonline.com/common/discovery/v2.0/keys
User name field = email
Kari Ruissalo (WyW)
01/20/2021, 12:53 PMremoved the graph endpoint but error remains the same... I'm just wondering that should I use the App Registration Value or ID for the Client Secret?
Kari Ruissalo (WyW)
01/20/2021, 12:54 PMyou can add client secrets via app registrations for the public ones apparently also...
Kari Ruissalo (WyW)
01/20/2021, 12:55 PMin AAD application I've set the redirect URI to https://gatewayFQDN/oauth/login
Kari Ruissalo (WyW)
01/20/2021, 12:57 PMoh, got it working now
Kari Ruissalo (WyW)
01/20/2021, 1:05 PMthank you @Frank Vandebergh, you showed me the way 🙂
2 Views