WSAS Security User and Role Management
Hello!
I am trying to get a better understanding on how these functions would be extended and used. If new roles were to be added such as subsets of users with users being assigned to those new roles, how does this segregation play itself out in the WSAS?
I can see immediate elements in the service execution, but I had been wondering about how else these new user functionality are impacted.
On a side note, I am running into in an issue with 2.3 where if I create a user called foo_user with a role called test_roles, and a default password. When they try to log in they are immediately hit with a "Invalid username/password" message. Even after bouncing Tomcat (WSAS is embedded servlet) it does not help.
Any insights are appreciated.
Thanks in advance!
Cheers!
- Login or register to post comments
- Printer friendly version
- 305 reads
Adding users and roles is
Adding users and roles is mainly releated to securing services using username token security configurations. So you can add a user or role, and assign that user or role to a service so that only that user or a user having that role can access the service.
Regarding your issue, only user who have the role "admin" assigned to them can login to the WSAS Management Console, which is a security feature.
Regards
Afkham Azeez