[kontinuity-dev-public] Creating a Project on Behalf of Users

[Ben Parees]

adding david back to the thread.


On Fri, Apr 15, 2016 at 3:19 PM, Andrew Lee Rubinger <alr at redhat.com> wrote:

>
>
> On Fri, Apr 15, 2016 at 3:11 PM, Ben Parees <bparees at redhat.com> wrote:
>
>>
>>
>> On Thu, Apr 14, 2016 at 8:11 PM, Andrew Lee Rubinger <alr at redhat.com>
>> wrote:
>>
>>> So the Catapult project will be creating OpenShift projects for its
>>> users.
>>>
>>> At the moment we're doing this by logging in *as* the user, but really
>>> what we want to do is create projects *on behalf of* users.
>>>
>>
>> ​can we take a step back and ask why logging in as the user and doing
>> stuff for them is not a valid approach for you?
>>
>
> Sure.
>
> 1) It's icky and has a weird audit trail, but more practically:
> 2) How do I get the user's login information (username and password)?
>
> S,
> ALR
>
>
>> ​
>>
>>
>>
>>>
>>> Clayton advises that we're unlikely to be granted cluster-admin rights
>>> to OpenShift Online (or even in some dedicated instance we run), so perhaps
>>> we need some other role that has permissions to create projects and a
>>> rolebinding to the user in question.
>>>
>>> Associated Catapult issue is:
>>>
>>>   https://github.com/redhat-kontinuity/catapult/issues/18
>>>
>>> Thoughts from the OpenShift team?
>>>
>>> S,
>>> ALR
>>>
>>> _______________________________________________
>>> kontinuity-dev-public mailing list
>>> kontinuity-dev-public at redhat.com
>>> https://www.redhat.com/mailman/listinfo/kontinuity-dev-public
>>>
>>>
>>
>>
>> --
>> Ben Parees | OpenShift
>>
>>
>


-- 
Ben Parees | OpenShift
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/kontinuity-dev-public/attachments/20160415/ae4c72e3/attachment.htm>