Bug 1104107 - [RFE][AAA] support only UPN format for usernames
Summary: [RFE][AAA] support only UPN format for usernames
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: AAA
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: ovirt-4.0.0-alpha
: 4.0.0
Assignee: Ravi Nori
QA Contact: Gonza
URL:
Whiteboard:
Depends On: ovirt-aaa-sso
Blocks: oVirt-AAA-rewrite
TreeView+ depends on / blocked
 
Reported: 2014-06-03 10:00 UTC by Yair Zaslavsky
Modified: 2016-07-15 05:38 UTC (History)
14 users (show)

Fixed In Version: ovirt 4.0.0 alpha1
Doc Type: Enhancement
Doc Text:
The SAM user format of profile\user is no longer supported.
Clone Of:
Environment:
Last Closed: 2016-07-05 07:52:16 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.0.0+
pnovotny: testing_plan_complete+
rule-engine: planning_ack+
alonbl: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)

Description Yair Zaslavsky 2014-06-03 10:00:06 UTC 
Description of problem:

From looking at REST-API code I saw there is support (probably back from 2.2 days) for domain\user format.
This support should probably be removed.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Yair Zaslavsky 2014-07-26 13:06:48 UTC 
This collides with BZ1123545.
Turns out that is still still used.
So we should reach a decision whether to support non UPN formats or not.

If we we do want to fix  PROFILE\user format, the fix should be around

BasicAutnenticationFilter.java

And also check the web.xml of the rest-api - web-app -


 <filter>
    <filter-name>BasicAuthenticationFilter</filter-name>
    <filter-class>org.ovirt.engine.core.aaa.filters.BasicAuthenticationFilter</filter-class>
    <init-param>
      <param-name>user-name-format</param-name>
      <param-value>UPN</param-value>
    </init-param>
  </filter>
Comment 4 Alon Bar-Lev 2015-11-17 12:43:04 UTC 
In 4.0 we can just drop this, no need to be backward compatible.
Comment 5 Alon Bar-Lev 2015-12-01 09:13:07 UTC 
Ravi, this should be trivial.
Comment 6 Ravi Nori 2015-12-01 15:22:28 UTC 
Fixed as part of SSO work
Comment 7 Red Hat Bugzilla Rules Engine 2015-12-01 15:26:00 UTC 
Fixed bug tickets must have version flags set prior to fixing them. Please set the correct version flags and move the bugs back to the previous status after this is corrected.
Comment 8 Red Hat Bugzilla Rules Engine 2015-12-01 15:26:00 UTC 
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
Comment 9 Red Hat Bugzilla Rules Engine 2015-12-01 15:26:00 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 10 Red Hat Bugzilla Rules Engine 2015-12-01 15:27:50 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 11 Red Hat Bugzilla Rules Engine 2015-12-01 15:27:50 UTC 
This request has been proposed for two releases. This is invalid flag usage. The ovirt-future release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.
Comment 12 Gonza 2016-06-15 09:08:06 UTC 
Verified with:
ovirt-engine-4.1.0-0.0.master.20160605051229.gitb398fa2.el7.centos.noarch
Comment 13 Sandro Bonazzola 2016-07-05 07:52:16 UTC 
oVirt 4.0.0 has been released, closing current release.
Note You need to log in before you can comment on or make changes to this bug.