@ScooterTheTroubleshooter, I believe you do not need to manipulate the high security settings for this integration. You only need to mark you AZURE AD admin user an "Internal Integration User". It is a check box on the user record.
This is very good. Most of my clients wants this auto provisioning from azure. And we do regularly face these same issues and prefer only the ldap path. But sincerely isn't there any other options? Ms and snow are now close partners can't they have a spoke based solution ? I should be able to run a schedule job every x minutes and pull in users and transform attributes? Any idea if they are going that way?
This video is very good, thanks, however I have a question. I have auto provisioning setup, but the naming convention in AD is not user friendly, so I renamed the groups in ServiceNow, I noticed the following, in the next provisioning the groups name does not change in snow however I did a restart of the provisioning and the group names in snow changed back to same name as in AD which is unfriendly, does somebody know why this happened?
This integration is so against best practices it makes me cry. Totally not valid approach. Neither from security perspective not from any maintainability perspective. I was really disappointed when I tested it.
@@jibzeejay4209 First of all, the connection. You have to generate an account and provide credentials, which are stored somewhere. This is bad, you should use OAuth or some token based auth. Another thing is that you are allowing or giving basically admin rights out. Also not good. Then, integrating directly through table API is not recommended. Simply, because there is no control over what you receive and you should not allow it. Even from trusted sources. Ideally, always integrate to SN through some custom API or import set table.
@ScooterTheTroubleshooter, I believe you do not need to manipulate the high security settings for this integration. You only need to mark you AZURE AD admin user an "Internal Integration User". It is a check box on the user record.
Correct. I've tested it, works fine. Don't need to change hi sec rules.
This is very good. Most of my clients wants this auto provisioning from azure. And we do regularly face these same issues and prefer only the ldap path. But sincerely isn't there any other options? Ms and snow are now close partners can't they have a spoke based solution ? I should be able to run a schedule job every x minutes and pull in users and transform attributes? Any idea if they are going that way?
Great Video, Thank you!
Thanks for the video. Do you know how to handle reference fields like department, location, cost center etc.?
Where is the article you mentioned in 7:55?
This video is very good, thanks, however I have a question. I have auto provisioning setup, but the naming convention in AD is not user friendly, so I renamed the groups in ServiceNow, I noticed the following, in the next provisioning the groups name does not change in snow however I did a restart of the provisioning and the group names in snow changed back to same name as in AD which is unfriendly, does somebody know why this happened?
Hi i have issue i dont see the test group i see on user in the mapping field is there something am missing it.
Much appreciated, can you please provide an alternative solution to mapped department field
Why do we have to disable those security settings?
Hi,
Thanks for the video.
How can import the photo to service now?
Thanks
This integration is so against best practices it makes me cry. Totally not valid approach. Neither from security perspective not from any maintainability perspective. I was really disappointed when I tested it.
@@jibzeejay4209 First of all, the connection. You have to generate an account and provide credentials, which are stored somewhere. This is bad, you should use OAuth or some token based auth.
Another thing is that you are allowing or giving basically admin rights out. Also not good.
Then, integrating directly through table API is not recommended. Simply, because there is no control over what you receive and you should not allow it. Even from trusted sources.
Ideally, always integrate to SN through some custom API or import set table.