-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Truncation of Large IDP Metadata in SAML IdP Metadata-field #13226
Comments
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can. |
I suspect the right solution here is to change to a larger TEXT blob format, probably with a migration. |
|
Hmm okay, how would i do that? In the db? |
@paegelow give me a few - I'll add a migration and then you can run the upgrade. |
You should be able to run the upgrade script now and the field should be changed to a MEDIUMTEXT field |
It worked! Really appreciate it! |
Debug mode
Describe the bug
I'm encountering an issue with the SAML IdP Metadata-field when handling large IDP metadata files. Despite the metadata file from our IDP provider being valid, it's getting truncated to around 65,000 characters when I attempt to insert it into the SAML IdP Metadata-field. This behavior persists regardless of whether I directly paste the XML data or insert the URL linking to it. This truncation causes information loss and hinders proper function.
Possible solutions would be to increase the character limit of the SAML IdP Metadata-field.
Any assistance or suggestions on how to handle large IDP metadata files without truncation would be greatly appreciated.
Thank you for your time and attention.
Reproduction steps
...
Expected behavior
No truncating
Screenshots
No response
Snipe-IT Version
v6.1.1-pre - build 10653 (master)
Operating System
Debian 11
Web Server
Apache
PHP Version
7.4.30
Operating System
No response
Browser
No response
Version
No response
Device
No response
Operating System
No response
Browser
No response
Version
No response
Error messages
Additional context
No response
The text was updated successfully, but these errors were encountered: