Multiple authorization types on a ledger-api

Hi team,

When enabling authorization on the ledger-api, we specify one type (be it a certificate, or jwks url, etc link). Is it possible to specify more the one type to handle different applications?

The context is like this. A participant node has already joined a domain, and that application requires “centralized IDM”, i.e. the user/jwt are centrally managed by the domain operator. When this participant node wishes to join another domain, they wish to have their own IDM. Ideally we can have something like “a set of DAR/templates” will be accessed through a specific type of authorization.

Thanks in advance.

kc

Yes, the documentation shows the type of auth-services to be a list. Just put a bunch of stuff in there.

Thanks @bernhard . I am assuming the list of items will be used to validate the tokens and it will get success as long as it is validated by one in the list. See if it’s the behaviour.

If that’s the case, can we limit this token corresponding to a specific set of DAR or template IDs or even a domain? Again, as said, we are building something like one participant node joining to more than one domain in this case.

Thanks again.

kc