Misc WARN messages in IdP v3-alpha2 logs

Cantor, Scott cantor.2 at osu.edu
Thu Jul 31 11:06:33 EDT 2014


On 7/31/14, 4:48 AM, "Kaspar Brand" <kaspar.brand at switch.ch> wrote:

>Maybe this could be lowered to INFO, given that these algorithms
>are denoted as optional in [1] and [2], respectively?

If we're going to assume WARN from OpenSAML is meaningful, I agree.

>2) net.shibboleth.idp.authn.principal.impl.GenericPrincipalSerializer
>
>With the native LDAP authentication, I'm seeing
>
>  WARN 
>[net.shibboleth.idp.authn.principal.impl.GenericPrincipalSerializer:113]
>- Unsupported Principal type will be omitted:
>org.ldaptive.jaas.LdapPrincipal
>
>whenever I authenticate. Is this expected, or could it point to
>an issue with my config?

It's expected (I don't think Daniel implemented a serializer for that
principal type), but I'm not sure it will be left at WARN.

I'm interested in input on what people think should be left on INFO at
all, let alone WARN, at this point. In particular, I'm not sure that
anything except a very minimum amount of transactional detail should be on
INFO. I'm thinking pretty much just a message about authentication
attempts suceeding or failing.

This is separate from the audit log, obviously, I'm talking about what
should show up for tracing under routine conditions when somebody just
successfully executes a transaction or fails a login. I can't really see
much point in adding anything to log on INFO that traces the flow of a
transaction other than the authentication step. Otherwise I think it's
just noise.

The SP is kind of at that point now when it's operating properly, there
really isn't much on INFO in the log anymore, deliberately.

-- Scott



More information about the dev mailing list