[satosa-users] binding a microservice to either a frontend or backend
22 May
2019
22 May
'19
11:49 p.m.
For the record: I mistook some redundant log entries and guessed that both Request and
Response micro services are called on both front- and backends.
For my education I traced the salient satosa classes and converted them to a few sequence
diagrams:
https://github.com/rhoerbe/SATOSA/tree/master/doc/internals
<https://github.com/rhoerbe/SATOSA/tree/master/doc/internals>
I hope it might be useful to others. I will make a PR later.
- Rainer
Am 2019-05-21 um 20:21 schrieb Rainer Hoerbe
<rainer at hoerbe.at>:
Am 2019-05-21 um 18:22 schrieb Scott Koranda
<skoranda at gmail.com>:
Hi,
Yes, I am using both. However, I need DecideIfRequesterIsAllowed only at the frontend,
and Consent and a custom ADFS-specific microservice only at the backend. While it does not
harm to have redundant initializations and invocations, it is cluttering the log file in
debug mode, and probably slowing down startup and processing.
- Rainer
_______________________________________________
satosa-users mailing list
satosa-users at lists.sunet.se
https://lists.sunet.se/listinfo/satosa-users Is there an option to limit a microservice to
either frontend or backend?
There are "request" microservices and "response" microservices. Is
that
enough for your use case?