I have the SMT server installed and configured based on the docs, but somethings seem missing or out of order in the docs.
I ran rcsmt status with the following results:
Using apache2 conf plugin /etc/apache2/conf.d/nu_server.conf
Using apache2 conf plugin /etc/apache2/conf.d/smt_mod_perl.conf
Not using apache2 conf plugin /etc/apache2/conf.d/smt_support.conf (SMT not enabled)
Using apache2 vhosts plugin /etc/apache2/vhosts.d/vhost-ssl.conf
Using cron plugin /etc/cron.d/novell.com-smt
Checking for httpd2: running
Checking for service MySQL: running
Checking for Cron: running
What did I miss that the smt_support.conf is not being used ? I’m also confused where and how to setup the certificate. There doesn’t seem to be anything in the docs about how to set it up. Of course I’ll probability find it right after i send this.
I currently can’t somment on the first part (smt_support.conf is not being used) as I have no live access to our server ATM.
If I remember correctly, you should have been creating a server certificate when installing the server system, using the YaST-CA. Of course you can as well use some different CA (like running a private, central CA for all your servers) and use a certificate generated by that.
Other than that, it’s “only” the certificate used by the Apache server to secure the SSL connection, so it’s the standard configuration for your Apache SSL vhost. IIRC the SMT configuration scripts copy the server cert to the root of the SMT server tree (so that the SMT cients can download it during their configuration steps), but no-one hinders you to specify a different certificate location when configuring SMT access in YaST on your SMT client systems. If you use your self-created certificates, it’d be less confusing to replace the SMT-installed copy with a copy of your own cert.
Had to install the smt proxy to get the smt-support.
I’m trying to register a client using the ./clientSetup4SMT.sh https://smt.example.com/center/regsvc but when I try the web url by itself I get a “bad request” is this normal ?
[QUOTE=cisaksen;24407]Had to install the smt proxy to get the smt-support.
I’m trying to register a client using the ./clientSetup4SMT.sh https://smt.example.com/center/regsvc but when I try the web url by itself I get a “bad request” is this normal ?[/QUOTE]
I haven’t tested that myself, but it may well be that the client uses POST, rather than GET, to communicate with the server.
If you encounter errors during clientSetup4SMT.sh, you may run the script with bash tracing (i.e. “bash -x ./clientSetup4SMT.sh https://smt.example.com/center/regsvc”) to see where it fails. In case you’re seeing problems during wget calls to your SMT server, check the server’s Apache log files for details.
Hi
Also note this may be a result of the server change to suse.com, you
need to ensure the smt it up to date and patched. I believe an email
went out to customers about the new SUSE Customer Center which also
included details about SMT?
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!