Project

General

Profile

Support #6037

Cassification de l'application Silverpeas, la documentation n'est pas à jour car ne correspond plus aux fichiers qu'on trouve sur le serveur

Added by Marc DENECHERE about 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Authentification
Target version:
-
Start date:
11/10/2014
Due date:
% Done:

100%

Estimated time:
Navigateur:
Tous
Votre version de Silverpeas:
5.14.2
Système d'exploitation:
Livraison en TEST:
Livraison en PROD:

Description

serveur cas : so-auth.mairie-aubervilliers.fr sur le port 443

La documentation du site Silverpeas n'est plus bonne par rapport à notre version et de plus on est pas sur d'être sur la bonne URL car on a du deviner l'URL.(pas de table de matière pour la documentation).

Voici les modification effectuée par mes soins sur le serveur de formation (10.2.3.149). :

vi /opt/jboss6/server/default/deploy/silverpeas/silverpeas.ear/war-ic.war/WEB-INF/web.xml

<context-param>
<param-name>serverName</param-name>
<param-value>http://localhost:8000&lt;/param-value>
</context-param>
<filter>
<filter-name>CAS Authentication Filter</filter-name>
<filter-class>org.jasig.cas.client.authentication.AuthenticationFilter</filter-class>
<init-param>
<param-name>casServerLoginUrl</param-name>
<param-value>https://ServerA:8443/cas/login&lt;/param-value>
</init-param>
<init-param>
<param-name>service</param-name>
<param-value>http://ServerB:8000/silverpeas/&lt;/param-value>
</init-param>
</filter>
<filter>
<filter-name>CAS Validation Filter</filter-name>
<filter-class>org.jasig.cas.client.validation.Cas20ProxyReceivingTicketValidationFilter</filter-class>
<init-param>
<param-name>casServerUrlPrefix</param-name>
<param-value>https://ServerA:8443/cas&lt;/param-value>
</init-param>
</filter>
<filter>
<filter-name>CAS HttpServletRequest Wrapper Filter</filter-name>
<filter-class>org.jasig.cas.client.util.HttpServletRequestWrapperFilter</filter-class>
</filter>

...
&lt;filter-mapping&gt;
&lt;filter-name&gt;CAS Authentication Filter&lt;/filter-name&gt;
&lt;url-pattern&gt;/*&lt;/url-pattern&gt;
&lt;/filter-mapping&gt;
&lt;filter-mapping&gt;
&lt;filter-name&gt;CAS Validation Filter&lt;/filter-name&gt;
&lt;url-pattern&gt;/*&lt;/url-pattern&gt;
&lt;/filter-mapping&gt;
&lt;filter-mapping&gt;
&lt;filter-name&gt;CAS HttpServletRequest Wrapper Filter&lt;/filter-name&gt;
&lt;url-pattern&gt;/*&lt;/url-pattern&gt;
&lt;/filter-mapping&gt;

vi /opt/silverpeas/properties/org/silverpeas/lookAndFeel/generalLook.properties

loginPage = AuthenticationServlet

vi /opt/silverpeas/properties/org/silverpeas/authentication/autDomainSP.properties

autServer0.type=org.silverpeas.authentication.AuthenticationCAS
autServer0.enabled=true
autServer0.SQLJDBCUrl=jdbcostgresql://localhost:5432/SilverpeasV5
autServer0.SQLAccessLogin=postgres
autServer0.SQLAccessPasswd=postgres
autServer0.SQLDriverClass=org.postgresql.Driver
autServer0.SQLUserTableName=st_user
autServer0.SQLUserLoginColumnName=login

vi /opt/silverpeas/properties/org/silverpeas/authentication/settings/authenticationSettings.properties

cas.authentication.domainId=0

et le message d'erreur :

http : 4040 -/ Silverpeas
The requested source (/Silverpeas) is not avalaible

#1

Updated by Marc DENECHERE about 6 years ago

Donc, pouvez vous nous fournir la documentation permettant de cassifier Silverpeas ou nous donner la procédure.

#2

Updated by Nicolas Eysseric about 6 years ago

  • Tracker changed from Bug to Support
  • Project changed from Silverpeas Components to Silverpeas Core
  • Target version deleted (Version 5.15)
  • Votre version de Silverpeas changed from 5.15-SNAPSHOT to 5.14.2
#3

Updated by David Lesimple about 6 years ago

  • Status changed from New to In progress...
  • Assignee set to Miguel Moquillon
#4

Updated by David Lesimple about 6 years ago

  • Category set to Authentification
  • Status changed from In progress... to Resolved
  • % Done changed from 0 to 100

La page de configuration de CAS était "cassée".
Celle-ci a été réparée et mise à jour.

#5

Updated by David Lesimple almost 6 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF