Skip to main content
Skip table of contents

Troubleshooting Login Issue with “Bad Request” Error After Update to UMS 12.08.100

After updating the IGEL Universal Management Suite (UMS) to the latest version 12.08.100, some users might see this error when trying to log in:
HTTP Status 400 – Bad Request
invalid_request – OAuth 2.0 Parameter: redirect_uri


Problem

This error appears when the web address (URL) you’re using to access UMS is not one of the approved addresses saved in the system settings. For security reasons, the system now only allows login links that match a list of “trusted addresses.”

Solution

Make sure you are using a login address that is allowed by UMS. Here are the valid types:

  • Local Address – for example: https://localhost:<ums-server-port>

  • Internal Server Address – for example: https://<server-address>:<server-port>

  • Cluster Address – for example: https://<cluster-address>

If you’re using a different address, the system will block the login attempt.

To fix the issue:

  1. Check and update your UMS settings to include the correct address(es). You may need to look in:

  2. After making changes, restart the UMS services to apply them.

Important Note

These settings don’t just affect login. Devices managed by UMS also need to reach these trusted addresses. Be sure all devices are using the correct one.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.