Resolve #36 by adding Proxy Ticketing for specially crafted SonarQube requests.
Because of SonarQube peculiarities a proxy ticket request can only successfully granted in the scope of the following requirements:
CAS must be able to validate proxy ticket under the CAS 3.0 specification
Sonar-CAS-Plugin must be configured for CAS 3.0 spec as well
the proxy ticket request must be in the form of a HTTP GET request with a basic authentication header following this form:
Authorization: Basic ${username}:ProxyTicket===:${proxyTicket} where the credential part is base64 encoded, following the usual RFC 7617 for basic authentication
Furthermore, this PR adds crucial information about the proxy ticketing workflow as well as ways to properly enable proxy ticketing via the SonarQube configuration
Resolve #36 by adding Proxy Ticketing for specially crafted SonarQube requests.
Because of SonarQube peculiarities a proxy ticket request can only successfully granted in the scope of the following requirements:
Authorization: Basic ${username}:ProxyTicket===:${proxyTicket}where the credential part is base64 encoded, following the usual RFC 7617 for basic authenticationFurthermore, this PR adds crucial information about the proxy ticketing workflow as well as ways to properly enable proxy ticketing via the SonarQube configuration