Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
06-28-2020 10:02 PM
Hello,
I have configured my service provider as per the following config.
SAML Authentication - 4.4.x Documentation - AppDynamics Documentation
Below is the error i get. The weird thing is there is no 'action' parameter meant to exist in the SAML 2.0 protocol
HTTP Status 400 - 'action' parameter must be specified
type Status report
message'action' parameter must be specified
descriptionThe request sent by the client was syntactically incorrect.
AppDynamics
06-29-2020 09:39 AM
Hi @Caleb.Ardern,
Thanks for your post on the community. I see you were looking at 4.4x documentation, here is a newer version of that document. https://docs.appdynamics.com/display/PRO45/Configure+Basic+SAML+Authentication
Please follow backup if you experience a different outcome with the latest documentation.
Thanks,
Ryan, Cisco AppDynamics Community Manager
Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Check out Observabiity in Action
new deep dive videos weekly in the Knowledge Base.
07-05-2020 02:29 AM
Hi Caleb
Could you provide some more info around what you are setting up..
1. What SAML Provider are you using, Azure Ad etc.?
2. Can you document a step by step setup procedure you followed?
3. I am assuming you are getting that error, after authenticating with your SAML IdP, when the IDP provider posts back the response to AppDynamics?
TO check this, you can install a SAML tracing extension in your browser, and then you can have a look at what SAML posts are being generated, that will significantly help in understanding where the problem is.
User | Count |
---|---|
4 | |
3 | |
3 | |
1 | |
1 | |
1 |
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form