-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Login with basic auth using username & password #89
Comments
tremes
added a commit
to tremes/openshift-rest-client
that referenced
this issue
Oct 29, 2018
…provided in user config
tremes
added a commit
to tremes/openshift-rest-client
that referenced
this issue
Oct 29, 2018
… provided in user config"
tremes
added a commit
to tremes/openshift-rest-client
that referenced
this issue
Oct 29, 2018
… provided in user config"
tremes
added a commit
to tremes/openshift-rest-client
that referenced
this issue
Oct 29, 2018
… provided in user config"
tremes
added a commit
to tremes/openshift-rest-client
that referenced
this issue
Oct 29, 2018
… provided in user config"
tremes
added a commit
to tremes/openshift-rest-client
that referenced
this issue
Nov 14, 2018
… provided in user config"
tremes
added a commit
to tremes/openshift-rest-client
that referenced
this issue
Nov 29, 2018
… provided in user config"
released as 1.6.0 |
Great. Thank you very much. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
AFAIK this is not possible now. I think this could be handy for example when using the openshift-rest-client in some nightly tests and especially handy in the case when the cluster is behind SSO (but oc is allowed to authenticate with just username/password).
I would like to try to work on this since I already have a POC working.
The text was updated successfully, but these errors were encountered: