Implement an ability to specify authenticated userIDs

[sleshchenko]

Hello, I'm from Eclipse Che team and we're trying to use OpenShift OAuth proxy for our needs.

In our scenario we need OpenShift OAuth Proxy to pass-user-bearer-token and this an ability exists 🎉
But we also need to restrict OpenShift OAuth Proxy to allow only one specific user.

I wonder if there are any thoughts against implementing an ability to specify authentication userIDs in the same way OpenShift OAuth proxy provides with -authenticated-emails-file.
Like -authenticated-ids-file or even -authenticated-ids.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[sleshchenko]

/remove-lifecycle rotten

[stlaz]

Hi,
As per #83, the authenticated emails don't really appear to work with the OpenShift auth provider and we would really like to scope the proxy down, so this is not likely to change. It's even questionable whether the downscoping is going to happen since "we" is "I" at this moment.

You might still be able to use the --openshift-sar option to do what you mean to do.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.