Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
There may be certain circumstances, when hiding functionality via links in the General Proxy Information section to things like the Knox Admin UI, Knox public certs, etc... is useful.
This improvement would allow for specific profiles to be defined within gateway-site.xml that would be referenced by name as a query param in the URL. A token profile will allow the homepage to filter itself based on the definition in gateway-site.xml to include only the links and topologies described in the profile.
This same feature would likely be able to be used as the default app on any topology endpoint. Instead of a 404 we could redirect to the homepage with an implied topology profile and the specific topology name.
This would lead us to a possible URL like:
https://localhost:8443/gateway/homepage/home?profile=topology&name=sandbox
This will tell it to filter for only the links described in the general topology profile and the indicated topology name and possibly with any additional topologies that are in the profile as well. Typically, I would imagine it to only have the one named in the query param but it would be up to the profile definition author.
Using the above idea, the token-based profile URL could be done in a similar way - so that it can differ the filter for token integrations, we would make it a different profile:
https://localhost:8443/gateway/homepage/home?profile=token&name=tokenbased
There should be 3 pre-configured profiles OOTB:
- full - all elements of GPI (General Proxy Information) is shown; no topology filtering
- thin - only the version and public certification elements are showing in GPI; no topology filtering
- token - only the version and token integration elements are shown in GPI; no topology filtering
Attachments
Issue Links
- links to
