-
Notifications
You must be signed in to change notification settings - Fork 481
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
Remember authentication details with endpoint configuration #1067
Comments
58 tasks
2 tasks
2 tasks
I had a look at how VS Code Docker Extension handles the passwords and noticed that:
|
Idea: Checkbox for remembering details |
Idea: Remember auth per endpoint url and the auth type. |
bpmn-io-tasks
bot
added
in progress
Currently worked on
and removed
ready
Ready to be worked on
labels
Oct 9, 2019
9 tasks
barmac
added a commit
that referenced
this issue
Oct 10, 2019
bpmn-io-tasks
bot
added
needs review
Review pending
and removed
in progress
Currently worked on
labels
Oct 10, 2019
Removed from #1439. We'll ship this with a future version of the tool. |
barmac
added a commit
that referenced
this issue
Oct 21, 2019
barmac
added a commit
that referenced
this issue
Oct 21, 2019
barmac
added
needs review
Review pending
in progress
Currently worked on
and removed
ready
Ready to be worked on
needs review
Review pending
labels
Oct 21, 2019
— with
bpmn-io-tasks
nikku
added
ready
Ready to be worked on
and removed
in progress
Currently worked on
labels
Oct 22, 2019
— with
bpmn-io-tasks
nikku
pushed a commit
that referenced
this issue
Oct 31, 2019
nikku
pushed a commit
that referenced
this issue
Nov 5, 2019
nikku
pushed a commit
that referenced
this issue
Nov 15, 2019
nikku
pushed a commit
that referenced
this issue
Nov 18, 2019
nikku
pushed a commit
that referenced
this issue
Nov 19, 2019
nikku
added a commit
that referenced
this issue
Nov 22, 2019
* remember authentication details, if the user actively decides this * restore global endpoint configuration, as intended until it is properly addressed via #804 * refactor deployment tool, pulling out validation into separate component * pull out menu update functionality to be re-added at a later point in time, in a different place * deployment tool UI remains untouched Closes #1067
nikku
added a commit
that referenced
this issue
Nov 22, 2019
* remember authentication details, if the user actively decides this * restore global endpoint configuration, as intended until it is properly addressed via #804 * refactor deployment tool, pulling out validation into separate component * pull out menu update functionality to be re-added at a later point in time, in a different place * deployment tool UI remains untouched Closes #1067
nikku
added a commit
that referenced
this issue
Nov 22, 2019
* remember authentication details, if the user actively decides this * restore global endpoint configuration, as intended until it is properly addressed via #804 * refactor deployment tool, pulling out validation into separate component * pull out menu update functionality to be re-added at a later point in time, in a different place * deployment tool UI remains untouched Closes #1067
nikku
added a commit
that referenced
this issue
Nov 22, 2019
* remember authentication details, if the user actively decides this * restore global endpoint configuration, as intended until it is properly addressed via #804 * refactor deployment tool, pulling out validation into separate component * pull out menu update functionality to be re-added at a later point in time, in a different place * deployment tool UI remains untouched Closes #1067
nikku
added
needs review
Review pending
and removed
ready
Ready to be worked on
labels
Nov 22, 2019
— with
bpmn-io-tasks
pinussilvestrus
pushed a commit
that referenced
this issue
Nov 22, 2019
* remember authentication details, if the user actively decides this * restore global endpoint configuration, as intended until it is properly addressed via #804 * refactor deployment tool, pulling out validation into separate component * pull out menu update functionality to be re-added at a later point in time, in a different place * deployment tool UI remains untouched Closes #1067
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
As a user I am frustrated if I need to re-configure the authentication details every time I re-deploy a diagram.
Describe the solution you'd like
config.json
upon successful deployment and restored on deploy dialog re-open.Describe alternatives you've considered
Don't store the details (password / token) if we don't find a way to secure it.
The text was updated successfully, but these errors were encountered: