Implement the user property for different connectors
Implement the user Property for both IFS10 and Oracle connectors and update the Login value for the Novacura user by replacing the same account name with an AD property value
-
Mahesh Wanigasooriya commented
Hi. The environments that we need this don't use OpenID. These are on our Offshore Rigs that use a On-premise AD.
Due to the merger, we are now having a AD where the samaccountname doesn't match the IFS directory IDs. We have a property within the AD where we can get the IFS User IDs.
What we are looking for is a way to use the IFS10 connector with connection being done via System account and a option to use a different Novacura User Property as the User ID to be passed to the connector.
We currently have around 10 rigs where this is a issue, but we will soon have all our Rigs (close to 30) using the new ADs, so we expect this to be more of a issue on all our Offshore environments.
-
Can you use UserNameClaimsKey property in OpenID and RunAs to support this requirement?