Solved

Azure AD authentication

  • 8 October 2021
  • 2 replies
  • 439 views

Userlevel 5
Badge +12

Hello Community,

Is it required to have local or public dns records for the redirect URIs when using Azure AD as the default authentication provider in Apps10?

 

For example in IFS documentation sample URI has to be in this format: 


https://test888.example.com:58080/main/ifsapplications/projection/oauth2/callback/

https://test888.example.com:58080/main/ifsapplications/web/oauth2/callback/

 

https://test888.example.com:58080/int/default/plsqlgateway/oauth2/callback

https://test888.example.com:58080/int/default/clientgateway/oauth2/callback

https://test888.example.com::58080/main/default/plsqlgateway/oauth2/callback

https://test888.example.com:58080/main/default/clientgateway/oauth2/callback

 

Is it necessary to have an local dns/ Azure DNS or public domain registration for below FQDN?

test888.example.com

icon

Best answer by Sajith D 10 October 2021, 23:27

View original

This topic has been closed for comments

2 replies

Userlevel 7
Badge +21

Hi @Ruchira ,

You don’t need public DNS records for the URL’s but would need local DNS so the client can be navigated redirected to the callback URL’s. The thing to keep in mind here is that Azure doesn’t communicate directly to the application URL’s. It will only instruct the client (i.e. client browser) to be redirected to the callback URL’s with the access token provided by Azure.

Cheers.

Userlevel 5
Badge +12

Hi @Ruchira ,

You don’t need public DNS records for the URL’s but would need local DNS so the client can be navigated redirected to the callback URL’s. The thing to keep in mind here is that Azure doesn’t communicate directly to the application URL’s. It will only instruct the client (i.e. client browser) to be redirected to the callback URL’s with the access token provided by Azure.

Cheers.

Thanks @Sajith D