Skip to content

Commit d3209e4

Browse files
Merge pull request #235167 from bhavana-129/predict-update
Updating Predict360 tutorial
2 parents e7f42b5 + 32cc94c commit d3209e4

File tree

1 file changed

+16
-7
lines changed

1 file changed

+16
-7
lines changed

articles/active-directory/saas-apps/predict360-sso-tutorial.md

Lines changed: 16 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
99
ms.subservice: saas-app-tutorial
1010
ms.workload: identity
1111
ms.topic: how-to
12-
ms.date: 04/06/2023
12+
ms.date: 04/20/2023
1313
ms.author: jeedes
1414

1515
---
@@ -69,25 +69,34 @@ Complete the following steps to enable Azure AD single sign-on in the Azure port
6969

7070
c. After the metadata file is successfully uploaded, the **Identifier** and **Reply URL** values get auto populated in Basic SAML Configuration section.
7171

72-
d. If you wish to configure the application in **SP** initiated mode, then perform the following step:
72+
d. Enter the customer code/key provided by 360factors in **Relay State** textbox. Make sure the code is entered in lowercase. This is required for **IDP** initiated mode.
73+
74+
> [!Note]
75+
> You will get the **Service Provider metadata file** from the [Predict360 SSO support team](mailto:[email protected]). If the **Identifier** and **Reply URL** values do not get auto populated, then fill in the values manually according to your requirement.
76+
77+
e. If you wish to configure the application in **SP** initiated mode, then perform the following step:
7378

74-
In the **Sign on URL** textbox, type the URL:
75-
`https://paadt.360factors.com/predict360/login.do`.
79+
In the **Sign on URL** textbox, type your customer specific URL using the following pattern:
80+
`https://<customer-key>.360factors.com/predict360/login.do`
7681

7782
> [!Note]
78-
> You will get the **Service Provider metadata file** from the [Predict360 SSO support team](mailto:[email protected]). If the **Identifier** and **Reply URL** values do not get auto populated, then fill in the values manually according to your requirement.
83+
> This URL is shared by 360factors team. `<customer-key>` is replaced with your customer key, which is also provide by 360factors team.
7984

8085
1. On the **Set-up single sign-on with SAML** page, in the **SAML Signing Certificate** section, find **Federation Metadata XML** and select **Download** to download the certificate and save it on your computer.
8186

8287
![Screenshot shows the Certificate download link.](common/metadataxml.png "Certificate")
8388

89+
1. Find **Certificate (Raw)** in the **SAML Signing Certificate** section, and select **Download** to download the certificate and save it on your computer.
90+
91+
![Screenshot shows the Certificate Raw download link.](common/certificateraw.png " Raw Certificate")
92+
8493
1. On the **Set up Predict360 SSO** section, copy the appropriate URL(s) based on your requirement.
8594

8695
![Screenshot shows to copy configuration appropriate URL.](common/copy-configuration-urls.png "Metadata")
8796

88-
## Configure Predict360 SSO SSO
97+
## Configure Predict360 SSO
8998

90-
To configure single sign-on on **Predict360 SSO** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Predict360 SSO support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
99+
To configure single sign-on on **Predict360 SSO** side, you need to send the downloaded **Federation Metadata XML**, **Certificate (Raw)** and appropriate copied URLs from Azure portal to [Predict360 SSO support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
91100

92101
### Create Predict360 SSO test user
93102

0 commit comments

Comments
 (0)