-
Notifications
You must be signed in to change notification settings - Fork 41.2k
Add CloudFoundry EndpointHandlerMapping #7108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
philwebb
pushed a commit
that referenced
this issue
Oct 12, 2016
Add an additional method to EndpointHandlerMapping which allows endpoints of a specific type to be returned. See gh-7108
philwebb
pushed a commit
that referenced
this issue
Oct 12, 2016
Update EndpointHandlerMapping so that it can be subclasses easily. Subclasses can override the `path` that is used to map the endpoint, allowing different mapping strategies to be used. See gh-7108
philwebb
pushed a commit
that referenced
this issue
Oct 21, 2016
Add a CloudFoundryEndpointHandlerMapping that can expose actuator endpoints for Cloud Foundry "appsmanager" to use. See gh-7108
philwebb
pushed a commit
that referenced
this issue
Oct 21, 2016
Update Cloud Foundry support with a discovery endpoint that shows what endpoints are available. See gh-7108
mbhave
added a commit
that referenced
this issue
Oct 24, 2016
philwebb
pushed a commit
to philwebb/spring-boot
that referenced
this issue
Nov 4, 2016
Add security to Cloud Foundry actuator endpoints. Security is enforced by a `HanderInterceptor` on `CloudFoundryEndpointHandlerMapping`. Each endpoint call expects an 'Authorization' header containing a bearer token. The token signature is checked against the UAA public keys then passed to the Cloud Controller to obtain an ultimate access level. The client may either have 'RESTRICTED' or FULL' access, with the latter only providing access to a limited set of endpoints. See spring-projectsgh-7108
philwebb
pushed a commit
to philwebb/spring-boot
that referenced
this issue
Nov 4, 2016
Change `CloudFoundryDiscoveryMvcEndpoint` so that `AccessLevel` rights are consulted so that only accessible links are returned. See spring-projectsgh-7108
philwebb
pushed a commit
to philwebb/spring-boot
that referenced
this issue
Nov 4, 2016
Update CORS configuration to support POST. See spring-projectsgh-7108
philwebb
pushed a commit
to philwebb/spring-boot
that referenced
this issue
Nov 4, 2016
Update CloudFoundrySecurityService so that SSL validation is not required. We're unlikely to have configured public keys for the REST endpoints we need to call. Since the endpoints are provided via environment variables we can implicitly trust them. See spring-projectsgh-7108
philwebb
added a commit
to philwebb/spring-boot
that referenced
this issue
Nov 4, 2016
Update `CloudFoundryActuatorAutoConfiguration` so that it is enabled when `management.cloudfoundry.enabled` is missing. See spring-projectsgh-7108
philwebb
pushed a commit
that referenced
this issue
Nov 5, 2016
Update CloudFoundrySecurityService so that SSL validation is not required. We're unlikely to have configured public keys for the REST endpoints we need to call. Since the endpoints are provided via environment variables we can implicitly trust them. See gh-7108
philwebb
added a commit
that referenced
this issue
Nov 5, 2016
Update `CloudFoundryActuatorAutoConfiguration` so that it is enabled when `management.cloudfoundry.enabled` is missing. See gh-7108
mbhave
added a commit
that referenced
this issue
Nov 7, 2016
Update CORS configuration to support Authorization and X-Cf-App-Instance. See gh-7108
mbhave
added a commit
that referenced
this issue
Nov 9, 2016
mbhave
added a commit
that referenced
this issue
Nov 9, 2016
The CloudFoundryHealthMvcEndpoint does not perform additional security checks since security is handled by the interceptor. See gh-7108
mbhave
added a commit
that referenced
this issue
Nov 11, 2016
mbhave
added a commit
that referenced
this issue
Nov 18, 2016
This interceptor processes the response with CORS headers and apepars before the Cloud Foundry security interceptor. See gh-7108
philwebb
added a commit
that referenced
this issue
Jan 4, 2017
Update configuration meta-data and appendix to include `management.cloudfoundry.*` meta-data. See gh-7108
philwebb
added a commit
that referenced
this issue
Jan 4, 2017
Add a Cloud Foundry specific section to "Production Ready Features". See gh-7108
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We need a variant of
EndpointHandlerMapping
that exposes actuator endpoints for Cloud Foundry to use.The endpoints should be exposed under
/cloudfoundryapplication
and should be present regardless of user endpoint settings. In addition the mapping must handle security.Tasks
/cloudfoundryapplication
The text was updated successfully, but these errors were encountered: