Differences

This shows you the differences between two versions of the page.

--- docpublic:systemes:shibboleth:spv2c7 [2015/08/07 15:20]
procacci@tem-tsp.eu [yum install]
+++ docpublic:systemes:shibboleth:spv2c7 [2017/02/21 09:42] (current)
procacci@tem-tsp.eu [Réference]
@@ Line 5: / Line 5: @@
   * https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPLinuxInstall
   * https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPGettingStarted
-  * https://federation.renater.fr/docs/installation#installer_un_sp_shibboleth
+  * https://services.renater.fr/federation/docs/installation#installer_un_sp_shibboleth
   * https://shib.kuleuven.be/docs/sp/2.x/install-sp-2.x-rhel.html
   * https://wiki.umn.edu/ShibAuth/Shibboleth2Xml
@@ Line 66: / Line 66: @@
 ==== demarrage automatique ====
-<code>
+je conseil d'installer le package bash-completion.noarch pour profiter de la completion des commandes systemctl
-[root@wood yum.repos.d]# systemctl list-units --all | grep -i shib
-shibd.service                           loaded inactive dead      LSB: Shibboleth 2 Service Provider Daemon
-[root@wood yum.repos.d]# systemctl enable shibd.service
+<code>
-shibd.service is not a native service, redirecting to /sbin/chkconfig.
-Executing /sbin/chkconfig shibd on
-The unit files have no [Install] section. They are not meant to be enabled
-using systemctl.
-Possible reasons for having this kind of units are:
-) A unit may be statically enabled by being symlinked from another unit's
-   .wants/ or .requires/ directory.
-) A unit's purpose may be to act as a helper for some other unit which has
-   a requirement dependency on it.
-) A unit may be started when needed via activation (socket, path, timer,
-   D-Bus, udev, scripted systemctl call, ...).
-[root@wood yum.repos.d]# chkconfig --list | grep shibd
-Note: This output shows SysV services only and does not include native
+[root@wikis yum.repos.d]# systemctl enable shibd.service
-      systemd services. SysV configuration data might be overridden by native
+ln -s '/usr/lib/systemd/system/shibd.service' '/etc/systemd/system/multi-user.target.wants/shibd.service'
-      systemd configuration.
-      If you want to list systemd services use 'systemctl list-unit-files'.
+[root@wikis shibboleth]# systemctl start shibd.service
-      To see services enabled on particular target use
+[root@wikis shibboleth]# systemctl status shibd.service
-      'systemctl list-dependencies [target]'.
+shibd.service - Shibboleth Service Provider Daemon
+   Loaded: loaded (/usr/lib/systemd/system/shibd.service; enabled)
+   Active: active (running) since Fri 2015-08-07 17:31:14 CEST; 4s ago
+ Main PID: 668 (shibd)
+   CGroup: /system.slice/shibd.service
+           `-668 /usr/sbin/shibd -f -F
-shibd          	0:off	1:off	2:on	3:on	4:on	5:on	6:off
+Aug 07 17:31:14 wikis systemd[1]: Started Shibboleth Service Provider Daemon.
 </code>
-et manuel la premiere fois:
-<code>
-# /etc/init.d/shibd start ; tail -f /var/log/shibboleth/shibd.log
-</code>
 Ainsi que httpd restart / reload pour charger le mod_shib contenu dans /etc/httpd/conf.d/shib.conf
@@ Line 153: / Line 138: @@
+==== test config ====
+attention à la libCurl et openssl :
+from https://wiki.infn.it/progetti/cloud-areapd/aai_integration_with_keystone/aai_integrations_with_openstack_keystone_icehouse#aai_integrations_in_openstack_keystone_icehouse
+<code>
+even if the message is marked as critical, those errors can be ignored. On many RedHat/Fedora installation a different version of libcurl is required, the library is located in /opt/shibboleth/lib64. The shibboleth daemon calls the configuration script /etc/sysconfig/shibd in order to overwrite the system library. In case it is possible to remove the error running the command
+LD_LIBRARY_PATH=/opt/shibboleth/lib64 shibd -t
+</code>
 ===== Parametrage shibboleth2.xml =====

docpublic/systemes/shibboleth/spv2c7.1438960827.txt.gz · Last modified: 2015/08/07 15:20 by procacci@tem-tsp.eu

Show page Old revisions

[unknown link type]Back to top