{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":40660,"path":"platform-security/authentication/t_EnableSvcProviderInitiatedAuth.md","title":"\\(Workaround\\) Enable service provider-initiated authentication","bundle":null,"doc_type":null,"release":"australia","body":"\n# \\(Workaround\\) Enable service provider-initiated authentication\n\nUse this workaround if authentication fails because you do not have SAML 2.0 Update 1. This issue can happen if users attempt to skip IdP authentication and navigate directly to the instance.\n\n## Before you begin\n\nRole required: sso\\_config\\_admin, business\\_rule\\_admin, script\\_include\\_admin\n\n## About this task\n\nThis error occurs when the instance doesn't provide ADFS with the needed definition and semantics for the SPNameQualifier attribute in the SAMLResponse.\n\nEnable service provider-initiated authentication by doing one of the following actions:\n\n## Procedure\n\n-   Upgrade to SAML 2.0 Update 1 and clear the option to create an AuthnContextClass request.\n\n-   Modify the **SAML2** script include to comment out the definitions of the `SPNameQualifier` attribute when you have SAML 2.0 active \\(not SAML 2.0 Update 1\\).\n\n    Comment out these lines in the createNameID and createNameIDPolicy functions:\n\n    ```\n    //nid.setSPNameQualifier (serviceURL ) ;\n    \n     //nameIdPolicy. setSPNameQualifier (serviceURLStr ) ;\n    ```\n\n\n## What to do next\n\nIf you do not want the login prompt from your ADFS server to appear when you access the instance, set the following SAML 2.0 Update 1 property to false: **Create an AuthnContextClass request in the AuthnRequest** statement \\(**glide.authenticate.sso.saml2.createrequestedauthncontext**\\).\n\n"}}