The CN must be a hostname without a protocol.
With the protocol the command even fails because of the missing escaping of the forward slashes:
openssl req -x509 -newkey rsa:2048 -keyout myservice.key -out myservice.cert -days 365 -nodes -subj '/CN=https://myservice.example.com'
Generating a 2048 bit RSA private key
..+++
...........................+++
writing new private key to 'myservice.key'
-----
end of string encountered while processing type of subject name element #1
problems making Certificate Request
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
When entering a resource name into the grant Resource text field, the user must select the resource from the dropdown below, and cannot simply click-off or tab to the next field without selection from the dropdown, or no resource will be selected.
* Explain in text and with screenshots how to correctly configure the Rancher SAML client in Keycloak, including mappers
* Provide examples for field configurations in Rancher that map to the Keycloak defaults
* Move the note on how to get a metadata.xml file with Keycloak >= 6.0.0 directly to the Prerequisites so that it is hard to miss
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
The AD attributes for the AD FS configuration do not match the description. The attributes `givenname` and `name` are reversed. Correcting to match expected output.
As rancher list the following global permissions:
Administrator
Administrators have full control over the entire installation and all resources in all clusters.
Standard User
Standard Users can create new clusters and manage clusters and projects they have been granted access to.
User-Base
User-Base users have login-access only.
if i understand correctly the concept i think that this should be reflected in the Readme file as well.
The AD attributes for the AD FS configuration do not match the description. The attributes `givenname` and `name` are reversed. Correcting to match expected output.
As rancher list the following global permissions:
Administrator
Administrators have full control over the entire installation and all resources in all clusters.
Standard User
Standard Users can create new clusters and manage clusters and projects they have been granted access to.
User-Base
User-Base users have login-access only.
if i understand correctly the concept i think that this should be reflected in the Readme file as well.
Bastian Hofmann
dkeightley
vcasado
Catherine Luse
Alex Seymour
Tejeev
David Noland
jgallucci32
Aleksandar Petreski
Ryan Elliott-Smith
Denise Schannon
Catherine Luse