Hi guys,
I see that there is not a web ui interface for setting user level ticket
policies?
Is there a particular reason for this? Just a curiousity.
Thanks
Marco
___
Freeipa-users mailing list
Freeipa-users@redhat.com
On 02/25/2012 07:53 AM, Marco Pizzoli wrote:
Hi, as you know I'm working with FreeIPA 2.1.90.
By following documentation I checked my tickets by issuing the klist
command but I'm obtaining an output slightly different than the one on
the doc.
[root@freeipa01 ~]# klist -kt /etc/krb5.keytab
On Sat, Feb 25, 2012 at 3:20 PM, Simo Sorce s...@redhat.com wrote:
On Sat, 2012-02-25 at 13:53 +0100, Marco Pizzoli wrote:
Hi, as you know I'm working with FreeIPA 2.1.90.
By following documentation I checked my tickets by issuing the klist
command but I'm obtaining an output slightly
On 02/25/2012 09:20 AM, Simo Sorce wrote:
Use -e to see what enctypes are reported.
Is this difference in any way related to s4u2proxy or did the extra
enctypes show up because we upgraded Kerberos and picked up other
unrelated behavior at the same time.
Why do we now have all these
On Sat, 2012-02-25 at 09:35 -0500, John Dennis wrote:
On 02/25/2012 09:20 AM, Simo Sorce wrote:
Use -e to see what enctypes are reported.
Is this difference in any way related to s4u2proxy or did the extra
enctypes show up because we upgraded Kerberos and picked up other
unrelated
On 02/25/2012 09:40 AM, Simo Sorce wrote:
Why do we now have all these enctypes? Is it to satify forwarding/proxy
when you don't know a prori which enctype the foreign endpoint will require?
Because in kerberos each principal can have multiple keys, generally one
per supported (by the KDC)
John Dennis wrote:
On 02/25/2012 09:40 AM, Simo Sorce wrote:
Why do we now have all these enctypes? Is it to satify forwarding/proxy
when you don't know a prori which enctype the foreign endpoint will
require?
Because in kerberos each principal can have multiple keys, generally one
per
