Since we are using SSO/SAML to authenticate our users in D360, do we need to create a service account that will act as an Application user to serve the purpose of it being the "Application" User for integration with other systems like Assure?
Unless there is a way in D360 to go bypass the SSO urls so it will go use the internal d360 users? Is that possible?
If I have a service account defined in our SSO/SAML, it will come in categorized as "user". Will this pose an issue if i use it as an "application" user? or can i change the categorization to Application instead of User?
Please sign in to leave a comment.