We can't remove "realms" qualifier unless the admin REST interface is
exposed under an entirely different WAR root context.
On 1/23/2015 10:28 AM, Bill Burke wrote:
On 1/23/2015 9:36 AM, Bill Burke wrote:
>
>
> On 1/23/2015 6:23 AM, Stian Thorgersen wrote:
>> Our URLs are quite long, examples:
>>
>> *
http://localhost:8080/auth/realms/master/protocols/openid-connect/login
>> *
http://localhost:8080/auth/realms/master/account
>>
>> We could remove the 'realms' part and 'protocols' parts
couldn't we?
>>
>> *
http://localhost:8080/auth/master/oidc/login
>> *
http://localhost:8080/auth/master/account
>>
>> That would require moving everything under a realm and I guess we'd need to
hard-wire the protocols, but I think that should be fine.
>>
>
> Wouldn't work for multiple reasons.
>
> * protocols/* exists to be able to plugin different protocols (oidc,
> saml, etc.)
> * Because of the crappy way JAX-RS dispatch algorithm handles wildcards
> for both resource classes and resource locators we need both a "realms"
> and "protocols" qualifier.
>
> Its really funny you bring this up now because I've renewed my argument
> with JAX-RS JSR just 2 minutes ago! Synchronicity!
>
Bah! Scratch that...I think we might be able to remove "realms" so long
as we don't add any other root context wildcard resource classes. Using
a wildcard only for "protocols" might paint us in a corner as there may
be other wildcard resources we want to add in the future.