[keycloak-dev] KC Auth Server Subsystem questions

Stan Silvert ssilvert at redhat.com
Sun Nov 2 17:34:10 EST 2014


I've update the PR with new documentation sections 3.3 and 3.5.  Also, 
the appliance dist and WildFly dist now include an updated version of 
the CLI/CLI GUI tool so you can upload keycloak-server.json, provider 
jars, and theme jars.

I've done a quick smoke test.  I'll be doing some more testing on it 
Monday morning.

On 11/1/2014 8:56 AM, Bill Burke wrote:
>
> On 11/1/2014 8:46 AM, Stan Silvert wrote:
>> On 10/31/2014 4:51 PM, Bill Burke wrote:
>>> * What are the benefits of it.  Specifically.  I'll need to state this
>>> in the release blog.
>>    * Support auth-server running in a WildFly domain (It's possible
>>      today, but this makes it much easier).
>>    * Eliminate deployment from /deployments directory to make it a proper
>>      service instead of an ordinary app.
>>    * Eliminate need to explode or crack open auth-server.war. Keep it
>>      intact so it doesn't need to be hacked up.
>>    * Load user-provided overlays for keycloak-server.json, SPI jars, and
>>      theme jars.
>>    * Allow uploading the above from CLI (and eventually from Keycloak
>>      Admin console).
>>    * Allow more than one auth-server in a WildFly instance.
>>
>>> * Where is the documentation for it?  Benefits, how to configure,
>>> manage?  How to add new providers?  Modify keycloak-server.json, etc...
>> Still working on the docs.  Stain brought up the point about
>> enabling/disabling confidential transport, which seems really
>> important.  So I'm adding that feature before I finish the docs.
> Honestly, confidential transport is not that important as Keycloak
> checks SSL settings every request anyways.  This is actually something
> we might want to add to the adapter's subsystem XML though.
>
>



More information about the keycloak-dev mailing list