@Sady_Rifat  the "path" must be an array.  Additionally ensure that idpCertAlias is not bound to any user. We just need to create a trust store, upload the certificate, make a note of the cert alias name and activate the trust store to publish  (/etc/truststore) via a package

@ayush_aem  regarding your question1. How do we invoke SAML authentication on click of login ? you need to do something similar to this:<a href="/system/sling/login?resource=/content/some/sso/protected/path.html&saml_request_path=/content/wknd/PageToBeShownAfterLogin.html">Login with SSO</a> The par...

@ayush_aem did you implement this functionality? If yes, could you post here how you resolved this? I too have a similar requirement where on login page (publish tier) I need to give two options to the users- login with SAML - SSO- login with form based authentication (username and password)1 On cli...

You must be able to edit the workflow as along as your ID has the correct group association. If you have used admin user to login to your local AEM, you must have an option to edit it too. Could you recheck the user ID with which you are logging in? If it is an non admin user, please add required AC...

 I got to know from wknd tech team that the request  was hitting the line https://github.com/adobe/aem-guides-wknd/blob/main/dispatcher/src/conf.d/available_vhosts/wknd.vhost#L89RewriteRule "^(.*)" - [R=204,L]I got to know that this will be addressed in the upcoming release.

@aanchal-sikka did you find a resolution to this issue? I'm also facing the same error with wknd code deployed on AEM as a cloud. One interesting observation is when I trigger the same post request through Postman /system/sling/login/j_security_check, the request does reach AEM publish and I get a 2...