Microsoft Azure single sign-on with Mercell
Contents
1 Configure single sign-on Azure
1.1 Configure Azure users
1.2 Note to PowerShell on Azure
2 Configure single sign-on Mercell website
3 For the customer's IT-department. Map own users
4 New Users
5 Change History Record
In the Identifier textbox, type the URL: https://my.mercell.com
Guide from Microsoft https://docs.microsoft.com/da-dk/azure/active-directory/saas-apps/media/mercell-tutorial/tutorial_general_203.png
If you need to extract AD user information, you can do it with PowerShell. Methods can be found on Microsoft Azure documentation.
https://docs.microsoft.com/en-us/powershell/module/azuread/get-azureaduser?view=azureadps-2.0
SSO Enforcement notice!
Please secure that all your user has been informed of the «SSO-Only» switchover, or they will see the screen below when they try to login manually without any success. (That is why it should be a planned date for going into production for all.)The same alert also happens, if you remove them from your local MS ADFS server.
If you usually use your corporate intranet for SSO login, then do as before.If you use an URL from Mercell, or connect directly to https://my.mercell.com, then you only need to click on the button called: «SSO login».
You will then have to enter your e-mail address as used in your company and click «Login». You will then be redirected to your own local SSO server, for a password. "Remember me" checkbox can be used to ensure that when accessing Mercell.com user is redirected directly to your own local SSO server. If login fails at local SSO server, user can access this page again and make changes.
After you entered your password inside your local corporate SSO server, then you will be redirected back to Mercell again, but you are now automatically logged into our portal.
You arrive either at your usual starting homepage, or at the specific Mercell URL you originally clicked on the first time.
Script for extracting user's that need to be mapped to Mercell.Script:
get-aduser -filter * | ft Name,UserPrincipalName > c:\test\test.txt (or preferably a CSV-file)
The result should look like this
Rabattavtale NO rabattavtale@mercell.com
IUSR_web1 IUSR_web1@mercell.com
PdfADev pdfadev@mercell.com
Test VPN tv@mercell.com
This script is used to do an AD BIND, which ensures that your existing users inside our portal are not asked to register as new users in our portal, when they start using the SSO. You can import this as Customer administrator by first "Export users". This will export an Excel file where only "User ID" is editable. Note that it is not allowed to rename this file as you will then not be able to import the file. Fill in "UserPrincipalName" in "User ID" save the file and "Import users". This will map the users already in Mercell to their AD user.
This can be repeated if new users' needs to be added. It can also be done on contact, (my.mercell.com/m/crm/customer.aspx – Contacts) where Customer Admin will have a new field "External User ID".
Note that if you have a user for restricted access named "(company name) SemiAnonymous users", it is important that this user has UserID SemiAnonymous, and this should not be deleted as this will remove access for the semi anonymous users.
Before starting the implementation, it is advisable to first do a startup meeting with Mercell, as there is some planning involved, and some steps to understand to not get duplicate problems or problems with users.
There is also a large impact on how the processes for creating new users are, both before, during and after the production. The success of the implementation will be determined on good control of the monitoring of this, as well as good communication with all relevant users involved.
When an unknown user (in the Mercell portal) logs in using SSO there are 3 possible settings. This setting applies for all users that are accessing through this connection as unknown users.
One of the above options must be chosen and will apply for all unknown users.
Ver.no |
Date |
Changed by (Doc.owner) |
Page |
Change |
Status |
Approved by |
Approved date |
V4 |
22.06.2018 |
KE |
All |
Updated with option for several customers on one connection, option to map user on contact. Updated screenshots and description for better user understanding. |
Approved |
CTO |
26.06.2018 |
V 4.1 |
02.11.2018 |
KE |
|
Enhanced sections 2 and 4 |
Approved |
CTO |
02.11.2018 |
V 4.2 |
17.06.2019 |
KE |
10 |
Added section about semi anon user |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|