Informix Error -26456: The authorization ID <%s> is not defined for the trusted context.
Cause and resolution
The authorization ID <%s> is not defined for the trusted context.
Authorization name <authorization-name> attempted to reuse a trusted connection using trusted context. The trusted context name can not be used under the <authorization-name>. The switch user failed. </authorization-name></authorization-name>
This error can also occur for one of the following reasons:
- The authorization ID is allowed to use the trusted context, but authentication is required and the request to switch users did not include the authentication token - The authorization ID is allowed to use the trusted context, but the trusted context is disabled - The system authorization ID attribute of the trusted context object associated with the trusted connection has been changed - The trusted context object associated with the trusted connection has been dropped
The attempt to reuse the trusted connection fails. The trusted connection is in an unconnected state.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-26456 fires when a switch-user attempt on a trusted connection fails — per the official guidance.
- The named authorization ID isn't defined to use the trusted context, per the official guidance — the first named case.
- The authorization ID is allowed, but authentication is required and the switch request didn't include the authentication token, per the official guidance — the second named case.
- The authorization ID is allowed, but the trusted context is disabled, per the official guidance — the third named case.
- The trusted context object's system authorization ID attribute has changed, per the official guidance — the fourth named case.
- The trusted context object associated with the trusted connection has been dropped, per the official guidance — the fifth named case; the trusted connection is left in an unconnected state.
Solutions / Resolution
- Check that the authorization ID is defined for the trusted context, and that authentication tokens/context status are correct, per the official guidance's implication, before retrying the switch.
Examples
N/A
No specific triggering statement is documented beyond a failed switch-user attempt on a trusted connection.
Diagnostic Checks
- Check the trusted context's defined authorization IDs, its enabled status, and whether it (or its system authorization ID) has changed/been dropped, and correct accordingly.
Related Errors / Related Topics
- -26459 — "The trusted context
does not exist." A related trusted- context error, on the context name itself being unrecognized rather than a switch-user failure against an existing one.
A switch-user attempt on a trusted connection failed — check the authorization ID's definition, authentication token, and the trusted context's status.