CESNET/perun — pull request #162 by zlamalp (2014-02-17 18:39:51+00:00)
Title: CORE, GUI: update URL path of Perun components

- Update URL paths to perun's components. We now specify
authz type before component's name:

e.g.: /perun-rpc-krb/ => /krb/perun-rpc/

Available authz types are: krb, fed, cert, non. If not present in URL,
Apache is expected to pick one of them as default.

For password-reset application using 'force-fed' is URL still same,
since it didn't have any other options then federated login. When
solution ensuring force reauthentication will be implemented, then
we can probably add support for other types to GUI links.

In perun-core Utils class use new and old variants to decide what
authz was used by user to ensure backward compatibility (I'm not sure,
if Apache sets original or new URL in HttpServletRequest when making redirect).

BEFORE ACCEPTING THIS COMMIT TO PRODUCTION:

- Update Apache configuration to provide redirects for old URLs, since
CESNET instance of Perun is already linked from outside web pages.
- Update Apache to correcly process new URLs.
- Update URLs in perun-registrar.properties and perun-rpc-lib.properties
files to use new scheme. Engine configuration shouldn't require
any intervention since it uses IPs or perun-rpc-lib component.

AFTER ACCEPTING THIS COMMIT TO PRODUCTION:

- Notify Meta and DU to update any links to Perun in their web pages.
- Update documentation on our wiki "Perun remote interfaces"
to present new URL scheme.

RESULT:

- As result of all this changes all Perun's components should be
always avilable on same host like this:

/[authzType]/perun-rpc/
/[authzType]/perun-gui/
/[authzType]/perun-registrar/
/[authzType]/perun-identity-consolidator/
/perun-password-reset/

where [authzType] can be empty (then apache will pick default)
or krb, fed or cert (or non - for registrar only).