Cornelius Kölbel

Maybe we simply need to make the `pw` token available in the UI. http --verify no POST https://localhost/token/init type=pw genkey=1 authorization:$TOK

The password token could be connected with one or many hostgroups #285. (Every tokentype could be connected with one or many hostgroups) Just like an SSH key or offline OTP...

> Let's find a simple way to provide a central way @katgirl Do you have a suggestion/idea how a user should manage an endless number of hostnames-and-passwords or applications-and-passwords? So...

> The token should be configurable like all tokens and should also be able to be displayed via the token list. It should also be possible to set a policy...

> Well, we've a similar problem. We authenticate Nextcloud-24.x against ADFS and use the privacyIDEA-ADFS-plugin for the second factor. This works perfectly for webbrowser and sync-clients because they open a...

> just as @stephanhendl has written. Let's find a simple way to provide a central way for certain "client" applications (delimited by policy) to allow users to continue using them...

> We use LDAP for logging in to the mail server (Dovecot/Postfix). > The webmailer (horde) itself does not log in against LDAP, but passes its credentials directly to the...

Could be also interesting for non-WebAuthn-Tokens. We could pass the IP based location in the pre-authentication.

Will be removed in 3.9 as communicated to users.

The node could be saved in the resolver itself. Usually this problem arrises from ldap resolvers and the server URI order should be node specific. The problem is, that the...