6:20 p.m.
Is there an option to limit a microservice to either frontend or backend?
If not, I would propose to extend MicroService with 2 bool args, like:
def __init__(self, name, base_url, backend=True, frontend=True, **kwargs):
Thanks, Rainer
8:21 p.m.
New subject: binding a microservice to either a frontend or backend
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
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?
11:49 p.m.
New subject: binding a microservice to either a frontend or backend
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? 
9:25 a.m.
New subject: binding a microservice to either a frontend or backend
Hi Rainer,
thanks for that, that is super user full!
Niels
On 22-05-19 23:49, Rainer Hoerbe wrote:
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
I hope it might be useful to others. I will make a PR later.
- Rainer
--
Niels van Dijk Technical Product Manager Trust & Security
Mob: +31 651347657 | Skype: cdr-80 | PGP Key ID: 0xDE7BB2F5
SURFnet BV | PO.Box 19035 | NL-3501 DA Utrecht | The Netherlands
www.surfnet.nl www.openconext.org
Am 2019-05-21 um 20:21 schrieb Rainer Hoerbe
<rainer at hoerbe.at
<mailto:rainer at hoerbe.at>>:
_______________________________________________
satosa-users mailing list
satosa-users at lists.sunet.se
https://lists.sunet.se/listinfo/satosa-users Am 2019-05-21 um 18:22 schrieb Scott Koranda
<skoranda at gmail.com
<mailto: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 <mailto: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?
1996
days inactive
1998
days old
4 comments
3 participants
participants (3)
-
niels.vandijk＠surfnet.nl -
rainer＠hoerbe.at -
skoranda＠gmail.com