Tutelar optionally calls an other application when a user register/login/removed etc. This calls are implemented in the HookService. The other application maybe require authenticating somehow. Currently we support Basic and Escher authentication.
The issue is implementing a third often used auth method: custom header with secret token.
hints:
it's basically same as the Basic auth
conf see application.conf:143com.wanari.tutelar.core.impl.ConfigServiceImpl#getHookConfigcom.wanari.tutelar.core.HookService.BasicAuthConfig
implement the auth method see com.wanari.tutelar.core.impl.HookServiceImpl#authenticator
write tests, see com.wanari.tutelar.core.impl.HookServiceSpec
Tutelar optionally calls an other application when a user register/login/removed etc. This calls are implemented in the
HookService
. The other application maybe require authenticating somehow. Currently we supportBasic
andEscher
authentication.The issue is implementing a third often used auth method: custom header with secret token.
hints:
Basic
authapplication.conf:143
com.wanari.tutelar.core.impl.ConfigServiceImpl#getHookConfig
com.wanari.tutelar.core.HookService.BasicAuthConfig
com.wanari.tutelar.core.impl.HookServiceImpl#authenticator
com.wanari.tutelar.core.impl.HookServiceSpec