I have two ways in which I want to customize the UAA:

- Brand the login screen with my company L&F
- Add descriptons for custom scopes so that the access confirmation
messages are relevant (currently defined in messages.properties [1] )

Do I need to fork the UAA and maintain that or is there an extension
process that I am not aware of?

Thanks,
John

[1] -
https://github.com/cloudfoundry/uaa/blob/bbea63986bbf2de9c42f231668e344a4a321184c/uaa/src/main/resources/messages.properties

No formal extension process currently exists to do what you're asking for.
The topic has been raised at the runtime PMC as others have similar needs.
It sounds like the identity team may have some plans to address that before
too long.

In the meantime, you can build your own login server and configure your
deployment to use it. It won't completely disable all of the branding that
exists in the UAA (another issue raised at the PMC) but my understanding is
that there are plans to address that too.

Sree, can you elaborate on any plans in this space?

Thanks.

On Mon, Nov 2, 2015 at 11:55 AM, john mcteague <john.mcteague(a)gmail.com>
wrote:

I have two ways in which I want to customize the UAA:

- Brand the login screen with my company L&F
- Add descriptons for custom scopes so that the access confirmation
messages are relevant (currently defined in messages.properties [1] )

Do I need to fork the UAA and maintain that or is there an extension
process that I am not aware of?

Thanks,
John

[1] -
https://github.com/cloudfoundry/uaa/blob/bbea63986bbf2de9c42f231668e344a4a321184c/uaa/src/main/resources/messages.properties

--
Matthew Sykes
matthew.sykes(a)gmail.com

Hi Josh,

Rebranding is possible today. This can be done by updating the assets under : https://github.com/cloudfoundry/uaa/blob/master/uaa/src/main/webapp/resources/

As mentioned by Matt below we do have plan for the removal of Pivotal Assets from the UAA open source repository. Please see below

Disable UAA Login
The first thing we will do is disabling the Login Server and allow the explicit configuration of an external login server. This would mean that the UAA UI pages will be no longer accessible and the info end point would return the login server location as the external login server.
The corresponding tracker story is here and is part of the current backlog of work.
https://www.pivotaltracker.com/story/show/106668494

Removal of Pivotal Assets
We have an internal project underway to create a Pivotal branded login and account management experience. Until this is done we will not be able to remove the Pivotal assets from the UAA open source repository. This work is currently slated to be competed in Q1 of 2016
You can track the story for Pivotal Assets removal here : https://www.pivotaltracker.com/story/show/106670296


Matt: Let's connect on the story to disable the external login server. I want to make sure that we have covered all the cases !


Thanks,
Sree

Sent from my iPad