It looks like the class: OAuth20AuthorizationCodeResponseTypeAuthorizationRequestValidator only checks for services based on client id and not service name. Since the service name is not checked the resulting service is null and the cache is never updated. On Monday, June 28, 2021 at 11:33:04 AM UTC-7 John Bergant wrote:
> I am trying to upgrade my *CAS* server to *6.3.3* from *6.2.8* and it > seems the OAuth flow is not working after the upgrade. In *6.3.x* there > was a feature added that cached registered services (here is the commit > <https://github.com/apereo/cas/commit/3c91ec4f7e124595a55eaa173fb7660833f69d1b>). > > When testing locally it seems like the cache is not being updated on a > miss. Other types of registered services rehydrate the cache on misses but > not the OAuth service. > > Am I missing a property that needs to be set on the Service so the cache > gets rehydrated? I took a look at the RegexRegisteredService and the > OAuthRegisteredService interface and I didn't see anything that would > indicate if the service should be cached. > > I am not using the Service Management, all my services are registered at > startup as beans and placed in a inMemoryRegisteredService Bean. > -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/83ecb2d3-f430-44dd-b794-095bac26f73an%40apereo.org.
