Nothing been changed, user getting started to not able to import model into Rhapsody DM project area
![]()
Env:Rhapsody DM 4.x, Websphere Server v8.0.x, Derby DB, Websphere Federated repository.
No change done on the User01 both for license and permission and project role info.
Later using User01 to add more user accounts in Websphere and JTS, and then assigned the floating license to each user account.
After repeating user login/logout for each new added user account successfully.
Login DM by User01 again and start to import model into the same project area, Client browser showing error message like " this user has no permission for this operation"
In dm.log, error message is "com.ibm.xtools.rmps.frontservice.jfsclient.RmpsRuntimeException: 400 (ERROR) :RHAPERR:invalidPermissions
"
In my understanding, only if design manager license is not granted or required roles are not assigned to the user, the import operation could be rejected.
Strange thing is, In this case, User01 has ever successfully imported a model into the same project area and no change been done on the User01 info itself. why after creating more user, suddenly importing operation is failed for User01?
Anyone can give me some hints?
Where I need to take a check?
What could be the possible causes?
Thank You
|
15 answers
![]()
Hi Jin,
I had a quick look at the code and it is possible that it is not in fact a license issue; rather, it could be a permissions problem. 1) Please go to https://servername:port/dm/admin and from the Project Areas menu, choose Active Project Areas. 2) Choose the project area where you are trying to perform the import. 3) Verify the correct process has been chosen -- although you cannot change it at this point, this affects the permissions. 4) In the Members and Administrators sections, verify the users who are trying to import are included appropriately (by clicking the Add... link). 5) Click on the Permissions link at the left of the page. 6) As a test to verify that this will resolve the issue, click Project Configuration and ensure all items in the Permitted Actions box are checked. 7) Repeat this with Team Configuration and ensure all items in the Permitted Actions box are checked. 8) Verify that the permissions problem is now resolved and the import now works. 9) Repeat steps 6 and 7 but set the permitted actions more selectively for security reasons. Comments Thank you for your suggestion.
Would have it a try and update you with the results.
Best Regards.
Have confirmed with the customer.
They have already checked all the access permissions to the role.
Issue's still there.
Regards
Hi Jin, you mentioned that they checked the access permissions to the role; however, I am wondering if they also checked the permissions to the "Everyone" role (in case the role that was expected was not assigned correctly to the user)?
In addition to the above, are the usernames ASCII characters?
|
![]()
Hi Jin, is the customer running WAS 8.0.0.3 or later? If they are can you check to see if they have the following custom property set in Session Management: InvalidateOnUnauthorizedSessionRequestException
This value can be found by logging into WAS Console and going to: Server->Server Types->WebSphere Application Server->Server1->Session Management->Custom Properties If it is not set then add the new variable and set it to true. Then Restart WAS and try the scenario again. There was a similar issue in CLM that caused problems when logging in and out of one user then logging in as a different user. The error was different but the scenario seems similar. In our case even though you logged out of one account and into another it still tried to use the credentials of the previous user. I think it is worth a try to see if this solves there problem. Comments Thank you, Peter.
Customer is actually using WAS 8.0.0.3.
As what you described, I have ever learnt in some cases, after logout from the previous user and login again with another user account, the previous user credential session could still be active and be reused. I suggested the customer clean the browser history and cookies before retrying import, but unfortunately the situation won't be improved.
I would ask the customer check the setting in WAS side you suggested above.
Since the customer first time successfully imported a model till the issue being detected, what customer has done to RDM and WAS is adding new users and assign licenses. But I think it's also possible customer forgot something they've done on the settings.
Hi, Peter
I think the problem is in the right hands but I wouldn't mind taking a look at the log files. Please forward all the logs you have to me.
|
![]()
Thank you, all
For your kind suggestion and spending time on the forum.
Best Regards
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.