From: Krzysztof B. <go...@ic...> - 2015-01-26 09:44:34
|
Hi, W dniu 23.01.2015 o 14:08, Terefang Verigorn pisze: > hi! > > now i am really stimped, the code in AuthenticatorImpl does not make > sense to me. Unfortunately for 1.4.0 code (I've forgot about this) there is no easy solution - you need to code the whole authenticator creation logic. What is hard as you noticed. Fortunately in 1.5.0 (expected this week) you will have additional internal API which is supporting a new sandbox authN feature. This should help you: i-face: pl.edu.icm.unity.server.api.internal.AuthenticatorsManagement with: /** * Resolves binding specific authenticator authN implementations for a given * list of {@link AuthenticatorSet}. * @param authnList * @return * @throws EngineException */ List<Map<String, BindingAuthn>> getAuthenticatorUIs(List<AuthenticatorSet> authnList) throws EngineException; BTW: internally you have two kinds of objects related to authenticatrs as one is intended for external users where details of an authenticator should be presented and internal objects which are supposed to work. Also the local verificators are configured, but implicitely - they rely on associated local credential's implementation, there is no need to introduce another configuration layer. HTH, Krzysztof |