Bug 1262229 - login with token , the Identity cannot be created when the identity of user was deleted
Summary: login with token , the Identity cannot be created when the identity of user w...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: apiserver-auth
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Jordan Liggitt
QA Contact: weiwei jiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-11 08:28 UTC by Wang Haoran
Modified: 2019-03-29 15:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-11 12:38:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Wang Haoran 2015-09-11 08:28:42 UTC
Description of problem:

when cluster admin delete the user identity, if the user login with token , the identity cannot be created
Version-Release number of selected component (if applicable):
oc v1.0.5-344-gd9fb965
openshift v1.0.5-344-gd9fb965
kubernetes v1.1.0-alpha.0-1605-g44c91b1

How reproducible:
always

Steps to Reproduce:
1. Login with a user1 (first time login)

2. delete the reference identity for the user with cluster admin

   oc delete identity <provider type>:<username>

3. Login with user1 again with token
   oc login  https://<master>:8443 --token=xxxxxxx
   
4. check the reference identity and useridentitymapping for the user1 

   oc get identity <provider type>:<username>

   oc get useridentitymapping <provider type>:<username>

Actual results:
after step 4, cannot get the identity and the mapping

Expected results:
after login , should get the identity and the mapping


Additional info:

Comment 1 Jordan Liggitt 2015-09-11 12:38:56 UTC
This is working as designed. The identity is only provisioned when logging in with the identity provider (username and password, for example). `oc login --token` does not follow the IdP->Identity->User path, it just authenticates using the token.


Note You need to log in before you can comment on or make changes to this bug.