-
Notifications
You must be signed in to change notification settings - Fork 58
Developer Sandbox Login experience enhancement #3838
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
Comments
Here's what I've figured out so far:
|
datho7561
added a commit
to datho7561/vscode-openshift-tools
that referenced
this issue
Jan 25, 2024
The service account will remain authenticated for longer than 15 minutes. To try this out: 1. Log into an OpenShift Sandbox cluster using the Login workflow 2. Run `oc whoami`. You should see a reference to `pipeline`, which is the serviceaccount that's being used 3. The Application Explorer should display you as logged in and work as expected Closes redhat-developer#3838 Signed-off-by: David Thompson <[email protected]>
datho7561
added a commit
to datho7561/vscode-openshift-tools
that referenced
this issue
Jan 29, 2024
The service account will remain authenticated for longer than 15 minutes. To try this out: 1. Log into an OpenShift Sandbox cluster using the Login workflow 2. Run `oc whoami`. You should see a reference to `pipeline`, which is the serviceaccount that's being used 3. The Application Explorer should display you as logged in and work as expected Closes redhat-developer#3838 Signed-off-by: David Thompson <[email protected]>
datho7561
added a commit
to datho7561/vscode-openshift-tools
that referenced
this issue
Feb 1, 2024
The service account will remain authenticated for longer than 15 minutes. To try this out: 1. Log into an OpenShift Sandbox cluster using the Login workflow 2. Run `oc whoami`. You should see a reference to `pipeline`, which is the serviceaccount that's being used 3. The Application Explorer should display you as logged in and work as expected Closes redhat-developer#3838 Signed-off-by: David Thompson <[email protected]>
datho7561
added a commit
to datho7561/vscode-openshift-tools
that referenced
this issue
Feb 1, 2024
The service account will remain authenticated for longer than 15 minutes. To try this out: 1. Log into an OpenShift Sandbox cluster using the Login workflow 2. Run `oc whoami`. You should see a reference to `pipeline`, which is the serviceaccount that's being used 3. The Application Explorer should display you as logged in and work as expected Closes redhat-developer#3838 Signed-off-by: David Thompson <[email protected]>
datho7561
added a commit
to datho7561/vscode-openshift-tools
that referenced
this issue
Feb 2, 2024
The service account will remain authenticated for longer than 15 minutes. To try this out: 1. Log into an OpenShift Sandbox cluster using the Login workflow 2. Run `oc whoami`. You should see a reference to `pipeline`, which is the serviceaccount that's being used 3. The Application Explorer should display you as logged in and work as expected Closes redhat-developer#3838 Signed-off-by: David Thompson <[email protected]>
vrubezhny
pushed a commit
that referenced
this issue
Feb 5, 2024
The service account will remain authenticated for longer than 15 minutes. To try this out: 1. Log into an OpenShift Sandbox cluster using the Login workflow 2. Run `oc whoami`. You should see a reference to `pipeline`, which is the serviceaccount that's being used 3. The Application Explorer should display you as logged in and work as expected Closes #3838 Signed-off-by: David Thompson <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Improve the developer sandbox login experience using Builder service account.
The text was updated successfully, but these errors were encountered: