Skip to content
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.

Ability to customize login server messages #536

Closed
wants to merge 1 commit into from
Closed

Ability to customize login server messages #536

wants to merge 1 commit into from

Conversation

fhanik
Copy link
Contributor

@fhanik fhanik commented Oct 22, 2014

https://www.pivotaltracker.com/story/show/71871918
This commit allows a new file to be configured
$CLOUD_COUNDRY_CONFIG_PATH/messages.properties
to contains custom messages for the login server.
This is useful when there is a need to display a description for a scope
during the OAuth user approval process of scopes/permissions

https://www.pivotaltracker.com/story/show/71871918
This commit allows a new file to be configured
$CLOUD_COUNDRY_CONFIG_PATH/messages.properties
to contains custom messages for the login server.
This is useful when there is a need to display a description for a scope
during the OAuth user approval process of scopes/permissions
@cfdreddbot
Copy link

Hey fhanik!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you've already signed the CLA.

@cf-gitbot
Copy link
Collaborator

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/81227916.

@fhanik
Copy link
Contributor Author

fhanik commented Oct 23, 2014

Not sure why CLA is being requested. pivotal.io email used.

@dieucao
Copy link

dieucao commented Oct 23, 2014

@fhanik The message is saying that you're covered by the CLA.

@fhanik
Copy link
Contributor Author

fhanik commented Oct 23, 2014

Commit has been included in @mbhave PR #528

@fhanik fhanik closed this Oct 23, 2014
@fhanik fhanik deleted the feature/ability-to-customize-login-server-messages branch February 13, 2015 17:15
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants