Managing authorizations Certificates
U41855-J-Z125-3-76 317
Dokuschablonen 19x24 Version 7.4de für FrameMaker V7.x vom 09.02.2010 © cognitas GmbH 2001-2010
19. March 2018 Stand 18:25.48 Pfad: P:\FTS-BS\Server\SE-Server\SE-Doku\1303912_BuV_062\BuV_e\buv.k11
12.3.2.1 Using the standard certificate
A self-signed, system-specific certificate is preinstalled on the SE server. This is not known
directly by the web browsers, nor is it derived from a known root certificate.
A standard certificate is automatically generated and activated each time the system is
renamed (the FQDN is changed). The new standard certificate must then of course be
accepted by or imported to the browsers.
The main features of this certificate are:
● The common name (CN) is identical to the fully qualified domain name (FQDN) of the
base operating system.
● The Validity time is 10 years.
● The fingerprint which unambiguously identifies the certificate is generated using the
SHA-1 algorithm and RSA encryption.
As the browser does not know the self-signed certificate, when the SE Manager is called it
requests the user to accept the certificate temporarily for the current session or to import it
permanently.
If you call the SE Manager on the local console, you must also confirm or import the
standard certificate, because the browser used on the Gnome desktop does not know the
certificate, either.
You are granted access to the SE Manager of the system component only if the certificate
is temporarily accepted or permanently imported.
If in doubt, you should first read and cross check the certificate before accepting it
temporarily or importing it permanently.
To Next Page
Loading...
Need help?
General