satanshiro

> Bumping this thread: the possibility of changing authority conditionally dynamically would be very useful because for example keycloak has the notion of realms and it is a normal use...

if you want to know the library is calling the introspect endpoint so have it work by calling it yourself first:  alternatively if you call the user info instead...

It depends on how you implemented it, at the end of the day if we want all js served from outside of keycloak whether lazy or not it won't make...

another reason to keep --external-assets would be browser optimizations, when navigating to a different html but with same script file imports. (I can't find documentation but this was common ground...

hey! will test pronto, and update. this feature comes right in time! thank you for your dedicated work!

hey! I'm closing the issue works great and tested on my end. thanks!

> The idea was to not have both `userManager` and `redirect_uri` + `client_id` + `authority`. In case you use the later one you can use in you application the type...

I took a look now and it's understandable, thanks have a nice day

hi unfortunately I can't test locally, I would like to try and do the following change to AuthProvider.tsx: ` return ( context ? ( {children} ): ( {children} ) );`...

this will probably help with peer dependency problems i'm having with terminus as it's using a different mikro orm version. hope this gets merged