Jeevan Desarda: Welcome back, everybody. Now in this
particular video, we can see how to roll out the single
sign-on for end-users.
Rolling out the single sign-on for an application is a
six-step process. The first and foremost thing which you
have to do is configure and test the single sign-on. You
have to work with that vendor to configure this particular
application and test the single sign-on.
As you are going to change the authentication type for users,
you have to plan the change cut over timelines. The timelines
has to be defined. You also have to communicate with the
users these particular timelines so that they get enough
amount of time to understand how the change is going to
happen.
Another important thing, or the next important thing
we heard is you have to train your support team. If the users
are going to have issues, they will call support team, so
support team have to be ramped up and provide appropriate
training for all these particular authentication changes.
We also suggest that you should prepare an FAQs and
provide that particular FAQs to your support team so that
when they receive questions, they know the answers about it.
At the final cut over, perform the testing with all your
business users and with all your scenarios, which includes
devices, users, network boundaries, etc. Once the integration
test is successful, you can do the cut over and you can
enable this particular SSO or single sign-on for all the users.
Now, we will see how the end-users are going to use these
applications. Our recommended way is using Access Panel.
Access Panel is nothing but it's a one experience for the
user where they can find all their apps and invoke the single
sign-on for any app they want, whether it will a line of
business application or it will be a SaaS application, they
can still able to use that. We have provided a search ability
where they can able to search the application and use that
if the list is very big.
Azure AD will not ask for authentication again for any app
because users has already authenticated to log in into the
Access Panel. User also can self-discover the apps by clicking
on the Add App button. The Add App button provides our
discoverability of the apps which organization has provided
them, so that they can request access and can use those apps.
Now, we will see how to use Access Panel for end-user
experience.
The short URL for the Access Panel is myapps.microsoft.com,
and with that, we can able to log in with your Azure Active
Directory credentials and can see all the apps which have
been assigned to use. They can able to search any app
which they want or they can directly click on the app to
invoke the single sign-on.
Here, I'm going to invoke Salesforce as an application, and
I can find that particular application to use. There is also
an Add Application button. By clicking on the Add Application
button, it gives the suggested applications. If there are no
applications assigned, they don't see it. But if there are
applications which have been given as a discovery for the
users by an organization, they can able to see that.
Now, we will see how the service provider initiated or the
app initiated single sign-on.
In this process, the user actually directly goes to that
particular application page and invokes the single sign-on.
They might know about that particular URL or they might
have bookmarked that application URL in their browser.
We will see how this experience looks like for a user for
Salesforce application.
Now, a user types in the URL for Salesforce application and
we will see how they can invoke the single sign-on. Here
in this particular screen, I have typed in my Salesforce
instance URL for our organization. And now I do see this
particular kind of page for login. Here, I have an organization
which is simply Test Azure AD and this login button up here
is over here. I don't see the normal username and password
page. When I click on this particular page, user will be
redirected for Azure Active Directory authentication. After
the authentication, they can directly able to login into
Salesforce. They will not be prompted for any username
and password if they have already logged in into any of the
applications which is enabled for single sign-in. If they
have not logged in into any of the applications, then Azure
AD will prompt for authentication where they have to put
their username and password and after that they can log in.
This is how the experience looks like for a user, which is
very streamlined and more secure for the organization.
Thank you for watching this video.
Luis Leon Plata: Yeah, thanks for watching this video and
listening to Jeevan and me. Hopefully this helps you guide
you in how to set up single sign-on with Azure AD. For more
information, visit the website in the banner below.