Why am I getting Status 404 -- Not Found Error on Azure?
F
Fathia Jama
started a topic
over 2 years ago
Why am I getting Status 404 -- Not Found Error on Azure?
Best Answer
F
Fathia Jama
said
over 2 years ago
When configuring SSO using Azure Active Directory, users may encounter the error below.
In many cases, this points to an issue with the Semarchy.xml configuration. Open the xml file in a text editor/viewer like Note++ to inspect the properties.
Check the official documentation and verify the issuer is properly configured. In our scenario, it is incorrect. Change the value according to step 20 of the xDM on Azure Installation Guide.
Restart the machine after any changes to the xml file, and re-test the operation.
1 Comment
F
Fathia Jama
said
over 2 years ago
Answer
When configuring SSO using Azure Active Directory, users may encounter the error below.
In many cases, this points to an issue with the Semarchy.xml configuration. Open the xml file in a text editor/viewer like Note++ to inspect the properties.
Check the official documentation and verify the issuer is properly configured. In our scenario, it is incorrect. Change the value according to step 20 of the xDM on Azure Installation Guide.
Restart the machine after any changes to the xml file, and re-test the operation.
Fathia Jama
Why am I getting Status 404 -- Not Found Error on Azure?
When configuring SSO using Azure Active Directory, users may encounter the error below.
In many cases, this points to an issue with the Semarchy.xml configuration. Open the xml file in a text editor/viewer like Note++ to inspect the properties.
Check the official documentation and verify the
issuer
is properly configured. In our scenario, it is incorrect. Change the value according to step 20 of thexDM on Azure Installation Guide
.Restart the machine after any changes to the xml file, and re-test the operation.
Fathia Jama
When configuring SSO using Azure Active Directory, users may encounter the error below.
In many cases, this points to an issue with the Semarchy.xml configuration. Open the xml file in a text editor/viewer like Note++ to inspect the properties.
Check the official documentation and verify the
issuer
is properly configured. In our scenario, it is incorrect. Change the value according to step 20 of thexDM on Azure Installation Guide
.Restart the machine after any changes to the xml file, and re-test the operation.
-
xDM Compatibility with Java 17?
-
xDM on Docker
-
How to Upgrade Apache Tomcat?
-
Application Server Gives 404 Error
-
Amazon Aurora support
-
Change Prod Repository Type Without Reinstallation
-
Is It Possible to Import a V5.1.1 Data Model to V5.2.8?
-
"500 Internal Server Error" While Opening with Localhost
-
Enable Access to Azure File Storage?
See all 29 topics