PAW Mode 2 - External AD
Posted: Mon Apr 19, 2021 12:57 am
Hi Guys,
I am quite new to Active Directory authentication using tm1 (Mode 2 and 3).
I've noticed that is quite simple to configure architect to work with integrated login:
- TM1 authentication compares the user's domain-qualified Microsoft Windows login name to the contents of the UniqueID element of the }ClientProperties cube and if there is a match, the user is authenticated to TM1.
However I am still trying to understand how this process works for PAW. It seems there are more verification steps than architect to authenticate the user.
____________________________________________________________________________
I am trying to accomplish the following:
1-) Supposing I have tm1 server and PAW installed on oracle cloud.
2-) An external user_A from Company_A wants to connect to PAW from his browser (Chrome or Mozilla) using integrated Windows authentication.
3-) This user_A does not have access to oracle cloud, but he wants that PAW accepts integrated Windows authentication using credentials from his Company_A Ldap server.
4-) Oracle cloud does not use Company_A Ldap server (users can't login to oracle cloud machines). I just use ETLdap to export users UniqueID from Company_A Ldap server to }ClientProperties cube.
____________________________________________________________________________
It seems PAW Windows authentication login does not work the same way architect integrated login works. Using ETLdap to export users UniqueID from Company_A Ldap server to }ClientProperties cube is not enough to establish connection to user_A browser.
My question:
What else should I do in order to allow an external user to use PAW Windows authentication ? Do I need to use kerberos to allow this user_A ldap server ?
I am quite new to Active Directory authentication using tm1 (Mode 2 and 3).
I've noticed that is quite simple to configure architect to work with integrated login:
- TM1 authentication compares the user's domain-qualified Microsoft Windows login name to the contents of the UniqueID element of the }ClientProperties cube and if there is a match, the user is authenticated to TM1.
However I am still trying to understand how this process works for PAW. It seems there are more verification steps than architect to authenticate the user.
____________________________________________________________________________
I am trying to accomplish the following:
1-) Supposing I have tm1 server and PAW installed on oracle cloud.
2-) An external user_A from Company_A wants to connect to PAW from his browser (Chrome or Mozilla) using integrated Windows authentication.
3-) This user_A does not have access to oracle cloud, but he wants that PAW accepts integrated Windows authentication using credentials from his Company_A Ldap server.
4-) Oracle cloud does not use Company_A Ldap server (users can't login to oracle cloud machines). I just use ETLdap to export users UniqueID from Company_A Ldap server to }ClientProperties cube.
____________________________________________________________________________
It seems PAW Windows authentication login does not work the same way architect integrated login works. Using ETLdap to export users UniqueID from Company_A Ldap server to }ClientProperties cube is not enough to establish connection to user_A browser.
My question:
What else should I do in order to allow an external user to use PAW Windows authentication ? Do I need to use kerberos to allow this user_A ldap server ?