Bug 1097942 - User should not be able to change password if using openId login
Summary: User should not be able to change password if using openId login
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Zanata
Classification: Retired
Component: Security
Version: 3.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Carlos Munoz
QA Contact: Zanata-QA Mailling List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-14 22:31 UTC by Alex Eng
Modified: 2023-09-14 02:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-31 01:20:15 UTC
Embargoed:

Attachments (Terms of Use)

Description Alex Eng 2014-05-14 22:31:55 UTC 
Description of problem:
User should not be able to change password if using openId login

Version-Release number of selected component (if applicable):
3.4-SNAPSHOT

How reproducible:
Always

Steps to Reproduce:
1. Go to Zanata openId instance or setup an openid zanata instance.
2. Login into zanata, go to top right menu, "Dashboard" -> Settings -> Account

Actual results:
User are able to update/set password

Expected results:
User should not be able to update/set password

Additional info:
Comment 1 Damian Jansen 2014-08-27 04:56:46 UTC 
Is this an invalid use case? It seems this has been developed intentionally.
Comment 2 Carlos Munoz 2014-08-28 21:58:56 UTC 
On our test Open id instances we have enabled both internal and Open Id authentication, which means that users should be allowed to set/change their password. If however, we find that they are also allowed to do so on OpenId-only instances, then that should be corrected.
Comment 3 Zanata Migrator 2015-07-31 01:20:15 UTC 
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-437
Comment 4 Red Hat Bugzilla 2023-09-14 02:07:55 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.