tampler opened a new issue, #6520:
URL: https://github.com/apache/cloudstack/issues/6520
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
Core, API, UI
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.16.1
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
Ubuntu 21.10
KVM
##### SUMMARY
<!-- Explain the problem/feature briefly -->
May be related to #6427
When I try to authenticate against a commercial `SAML IdP`, I'm getting the
following error in my browser console:
`Status Code: 431 Request Header Fields Too Large`.
This error occurs when IdP redirects back to ACS with the following link
(trimmed):
`http://localhost:8080/client/api?command=samlSso?SAMLResponse=PHNhbWxwOlJlc3BvbnNlIH......`
NOTE:
I created a little SAML2.0 client in GO and was able to successfully
authenticate with my provider and my credentials
SAML responses
Working `demo` -
[here](https://gist.github.com/tampler/64a216f7bac52f8ec5de754d7a2835b4)
Failing `CloudStack` -
[here](https://gist.github.com/tampler/35ace1d02f91796cd8b60e82076953b2)
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
1. Enable SAML in global config
2. Change SAML IdP metadata to the proper IdP link. Validate the IdP
metadata link before using
3. Leave ALL other SAML related parameters default
4. Reboot mgmt server
5. Open mgmt login page and select `Single Sign-On`
6. Pick your IdP
7. Authenticate with your IdP with login and pass
8. Right after authn I'm getting redirected to the ACS page, which fails
with the error specified
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
SAML SSO allows to authenticate
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
SAML SSO returns an error code 431
~~~
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
