AuthorizationFailed error for a user defined in Jazz
We have one user defined in Jazz server of our 7.2.0.2 RAM server. When we are trying to access the Jazz server using that particular user credentials, we are getting the following error message :
Error 403: AuthorizationFailed
We don't have that user defined as WAS admin in our console.
Is this may be the reason of error?
If not, then what may be the reason of this authorization failure and how to fix it?
Error 403: AuthorizationFailed
We don't have that user defined as WAS admin in our console.
Is this may be the reason of error?
If not, then what may be the reason of this authorization failure and how to fix it?
3 answers
As a requirement to install RAM on WAS we are invited to configure the WAS Security section.
Ive always configured the WAS Security. On the RAMs installer/configurator we defined what is the auth method (system-based, LDAP,...). In fact, RAM/RTC admin doesnt need to be a WAS Admin, but the user defined as RAM or RTC (Its possible to be different or not in both servers) admin should exists on the auth-type selected.
This can be fixed running the installer/configurator (http://yourserver/ram.setup as default), on the repository settings you can define the user (or users) and check the authorization.
If I could realized your doubt, it should help you. Let me know that.
Ive always configured the WAS Security. On the RAMs installer/configurator we defined what is the auth method (system-based, LDAP,...). In fact, RAM/RTC admin doesnt need to be a WAS Admin, but the user defined as RAM or RTC (Its possible to be different or not in both servers) admin should exists on the auth-type selected.
This can be fixed running the installer/configurator (http://yourserver/ram.setup as default), on the repository settings you can define the user (or users) and check the authorization.
If I could realized your doubt, it should help you. Let me know that.