FWIW - a lot of the direct linking code is due to the fact there's not a public API (and all this code originated as an external plugin). That's an opportunity for code cleanup now that this plugin has access to the private Xrootd APIs. From the `ofs.authlib` point-of-view, an example of how it's loaded now is: ``` ofs.authlib libXrdMacaroons.so libXrdAccSciTokens.so ``` So, authorizations are first examined by `libXrdMacaroons`; if the result is inconclusive, then it's passed to `libXrdAccSciTokens`; if that result is inconclusive, then it is passed to the default plugin. @esindril - can you kindly remind me of the use case here? I recall talking about it but don't think I wrote it down. That is, if you have `libXrdAccEOS`, why doesn't the following work: ``` ofs.authlib libXrdMacaroons.so libXrdAccEOS.so ``` ? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/pull/1147#issuecomment-595014397 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1