Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
- Timestamp:
-
05/03/11 16:41:49 (13 years ago)
- Author:
-
jmoore
- Comment:
-
After talking to Ola, the decision was to add a method on omero.api.ServiceFactoryPrx allowing users to pass in their password changing the server-side boolean which tracks whether or not @RolesAllowed("HasPassword") should be considered true. This seems simpler than adding new methods (changeUserPasswordWithAdminPassword(string, string, string)) or adding a new exception (requiring clients to create a new session with the password, etc.)
I'll take over this for making the modifications, and then pass on to Ola.
Legend:
- Unmodified
- Added
- Removed
- Modified
-
-
Property
Status
changed from
new
to
accepted
- Property Cc atarkowska added
-
Property
Remaining Time
changed from
0.2
to
0.5
- Property Owner changed from saloynton to jmoore
-
|
v5
|
v7
|
|
| 10 | 10 | start creating new sessions with the new password |
| 11 | 11 | I realize that in the web scenario N-1 of the workers will have been authenticated with a session uuid, so if you receive a SecurityViolation you will need to re-authenticate, or create a temporary SSL-based omero.client with the real password. |
| | 12 | |
| | 13 | '''NB:''' This is a follow-on to #3201 |
1.3.13-PRO © 2008-2011
Agilo Software all
rights reserved
(this page was served in: 0.15364 sec.)
