As soon as you define a policy in scope “admin” (or scope “user”)
all admins are checked for policies.
Thus, if the original “superadmin” would not be located in
helpdesk-admin-policy, the superadmin will end up with no rights.
The best practice is to always start with a superadmin.
Thanks for reporting back.
CorneliusAm Montag, den 01.08.2016, 01:55 -0700 schrieb jmdeking:
My fault, i have to define 2 policy’s, 1 for the admin and 1 for the
helpdesk else by default you have no rights for the account that is
On Wednesday, July 27, 2016 at 1:41:58 PM UTC+2, jmdeking wrote:
I cant seem to wrap my head around this.
I make a simple admin policy using the template helpdesk and
fill in the field 'Admin' the local user helpdesk i created
but then i am also locked out with my default 'admin' account.
I read the docs multiple times but i dont understand how does
is supposed to work.
Please read the blog post about getting help
For professional services and consultancy regarding two factor
authentication please visit
In an enterprise environment you should get a SERVICE LEVEL AGREEMENT
which suites your needs for SECURITY, AVAILABILITY and LIABILITY:
You received this message because you are subscribed to the Google
Groups “privacyidea” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to firstname.lastname@example.org.
To post to this group, send email to email@example.com.
Visit this group at https://groups.google.com/group/privacyidea.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.
+49 151 2960 1417
Landgraf-Karl-Str. 19, 34131 Kassel, Germany
Tel: +49 561 3166797, Fax: +49 561 3166798
Amtsgericht Kassel, HRB 16405
Geschäftsführer: Cornelius Kölbel
signature.asc (836 Bytes)