Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Push EMail #3826

Closed
cornelinux opened this issue Nov 30, 2023 · 1 comment
Closed

Push EMail #3826

cornelinux opened this issue Nov 30, 2023 · 1 comment
Labels
Prio: Low Type: Idea! Discuss new ideas, features and enhancements

Comments

@cornelinux
Copy link
Member

With the PUSH token we deliver an authentication request to the user. By clicking yes and sending this yes to the privacyIDEA server, this authenitcation request is valid in the privacyIDEA server.

We could use this building blocks to create an Email Token, that sends a link in an email to the user.
Clicking the link would mark the authentication request as valid in the privacyIDEA server. The same workflow like with push tokens could continue.

Plus side: The user would not have to enter anything.

Down side: Besides security this could be confusing with all the windows:

  1. User tries to e.g. login in browser window A with keycloak.
  2. User has to open his email client and click ths link which would...
  3. ...open a browser window B...
  4. Then he would have to manually return to browser window A.
@cornelinux cornelinux added Type: Idea! Discuss new ideas, features and enhancements Prio: Low labels Nov 30, 2023
@nilsbehlen
Copy link
Member

The window handling becomes complicated and annyoing so we wont do that for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Prio: Low Type: Idea! Discuss new ideas, features and enhancements
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cornelinux @nilsbehlen