AW: Re: A bug und some ideas for privacyIDEA

Hi,
No need to be sorry. I created the issues yesterday.
So you do not need to create a github account. I will look into the user policy thing.
Thanks a lot and kind regards Cornelius

Cornelius KölbelCornelius.koelbel@netknights.it+49 151 2960 1417
NetKnights GmbHhttp://netknights.itLandgraf-Karl-Str. 19, 34131 Kassel, GermanyTel: +49 561 3166797, Fax: +49 561 3166798
Amtsgericht Kassel, HRB 16405Geschäftsführer: Cornelius Kölbel-------- Ursprüngliche Nachricht --------
Von: juergen.f.koller@gmail.com
Datum: 16.10.2015 14:28 (GMT+01:00)
An: privacyidea privacyidea@googlegroups.com
Betreff: Re: A bug und some ideas for privacyIDEA

Sorry for being so late.

Am Donnerstag, 15. Oktober 2015 12:16:27 UTC+2 schrieb Cornelinux K:
Am Donnerstag, den 15.10.2015, 03:07 -0700 schrieb

juergen....@gmail.com:

  * How is it possible to define the scope of the LDAP searches?

Admitted: The scope is always “SUB”. Thus it will always look for users

within the specified BaseDN and underneath.

  * It would be nice to make the display PIN and OTP during 'Test
    Token' optional.

OK. Sounds sensible.

  * It would be nice to set the default token type in some of the
    config options.

You mean the default token type for “enroll token” in the UI?

  * It would be nice to set the Token Infos (validity...) during
    token enrollment.

Phew. You are one of the few who probably use the validity period :wink:

So setting it during enrollment is a real request.

I think there could be a checkbox, button or accordion, that can open

some details.

Setting the validity period during the API enrollment call is not

possible.

So probably we would have to improve the API, too.

I also found a small bug. If you edit the ‘Validity End’ of a pw

token, e.g. lostTOTP, then the date decremented by one. If you set

“Validity End” to “18/10/15” the value “validity_period_end:”

17/10/15 22:00.

Strange. Thanks a lot!

I will file some issues at github, later.

If you have the possibility to do so, you are welcome to file your

findings including my comments.

Should I get an account on github for you? :slight_smile: If this would be much easier for you, then I will get one. To add just one more bug:ich you set a policy with scoe user, then under “Users” there is an error :“User actions are defined, but this action is not allowed!”. Perhaps I only missed a button in the policy.
Jürgen

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 privacyidea+unsubscribe@googlegroups.com.

To post to this group, send email to privacyidea@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/privacyidea/bdcbeef1-fa5a-4dd0-b17c-babc816bcccf%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

You only get this error message, if the logged in user has the role “user”.Please check in the upper right corner in the UI which role you have.
A user should not see the user tab.
Logout and login.
Kind regards Cornelius

Cornelius KölbelCornelius.koelbel@netknights.it+49 151 2960 1417
NetKnights GmbHhttp://netknights.itLandgraf-Karl-Str. 19, 34131 Kassel, GermanyTel: +49 561 3166797, Fax: +49 561 3166798
Amtsgericht Kassel, HRB 16405Geschäftsführer: Cornelius Kölbel-------- Ursprüngliche Nachricht --------
Von: juergen.f.koller@gmail.com
Datum: 16.10.2015 14:28 (GMT+01:00)
An: privacyidea privacyidea@googlegroups.com
Betreff: Re: A bug und some ideas for privacyIDEA

Sorry for being so late.

Am Donnerstag, 15. Oktober 2015 12:16:27 UTC+2 schrieb Cornelinux K:
Am Donnerstag, den 15.10.2015, 03:07 -0700 schrieb

juergen....@gmail.com:

  * How is it possible to define the scope of the LDAP searches?

Admitted: The scope is always “SUB”. Thus it will always look for users

within the specified BaseDN and underneath.

  * It would be nice to make the display PIN and OTP during 'Test
    Token' optional.

OK. Sounds sensible.

  * It would be nice to set the default token type in some of the
    config options.

You mean the default token type for “enroll token” in the UI?

  * It would be nice to set the Token Infos (validity...) during
    token enrollment.

Phew. You are one of the few who probably use the validity period :wink:

So setting it during enrollment is a real request.

I think there could be a checkbox, button or accordion, that can open

some details.

Setting the validity period during the API enrollment call is not

possible.

So probably we would have to improve the API, too.

I also found a small bug. If you edit the ‘Validity End’ of a pw

token, e.g. lostTOTP, then the date decremented by one. If you set

“Validity End” to “18/10/15” the value “validity_period_end:”

17/10/15 22:00.

Strange. Thanks a lot!

I will file some issues at github, later.

If you have the possibility to do so, you are welcome to file your

findings including my comments.

Should I get an account on github for you? :slight_smile: If this would be much easier for you, then I will get one. To add just one more bug:ich you set a policy with scoe user, then under “Users” there is an error :“User actions are defined, but this action is not allowed!”. Perhaps I only missed a button in the policy.
Jürgen

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 privacyidea+unsubscribe@googlegroups.com.

To post to this group, send email to privacyidea@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/privacyidea/bdcbeef1-fa5a-4dd0-b17c-babc816bcccf%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.