500 Internal Server error when binding an application to a SSO service instance
Article ID: 293382
Updated On:
Products
Operations Manager
Issue/Introduction
When trying to bind an application to an instance of SSO you are receiving a 500 internal server error.
One of the causes is that SSO_REDIRECT_URI is too long. By design, the maximum allowed data entry is 1024 bytes, which includes escaped characters.
After you try to bind the application to the SSO instance, you will receive the following error message in the uaa.log from the UAA VM for TAS.
Example:
One of the causes is that SSO_REDIRECT_URI is too long. By design, the maximum allowed data entry is 1024 bytes, which includes escaped characters.
After you try to bind the application to the SSO instance, you will receive the following error message in the uaa.log from the UAA VM for TAS.
Example:
Data too long for column 'web_server_redirect_uri' at row 1; nested exception is java.sql.SQLDataException: (conn=11576828) Data too long for column 'web_server_redirect_uri' at row 1
Resolution
Ensure that your SSO_REDIRECT_URI is within the limit of 1024 bytes.
Some other configuration with longer than limit could result in similar 500 error, please review SSO broker logs and UAA logs. In case you can't resolve it, please open support ticket and attach SSO broker logs and TAS UAA logs.
Feedback
Yes
No
Powered by
