We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
at line 7 the # Autogenerated addresses example based in 19.168.135.0/24 -> I guess it should be 192.168.135.0/24
Do we have somewhere an example for an SMT/RMT server registration?
The text was updated successfully, but these errors were encountered:
The procedure could be like this for SLES15 SP2 and an SMT with self signed certificate:
wget https://<FQHN>/<name-of-crt>.crt --no-check-certificate cp <name-of-crt>.crt /etc/pki/trust/anchors/registration_server.pem update-ca-certificates SUSEConnect --url https://<FQHN>
that means we need two more variables: FQHN = "https://smtserver.customer.com" name-of-crt = "smt"
Sorry, something went wrong.
Thanks @pirat013 , Yes, the first one is a typo. Thank you for the report.
About the 2nd: As you say, we would need some new implementation, we never had the need to do so, but if it makes sense, we can include it.
We would add it as optional. If the user doesn't provide any of those parameters, we would use the standard url, and the provided ones otherwise.
Would this be good enough?
No branches or pull requests
at line 7 the # Autogenerated addresses example based in 19.168.135.0/24 -> I guess it should be 192.168.135.0/24
Do we have somewhere an example for an SMT/RMT server registration?
The text was updated successfully, but these errors were encountered: