TWiki>
LCG Web>YAIM>YaimGuide400>VOMS_configuration_variables (2008-07-29, MariaALANDESPRADILLO)
EditAttachPDF
LCG Web>YAIM>YaimGuide400>VOMS_configuration_variables (2008-07-29, MariaALANDESPRADILLO) EditAttachPDFConfiguration variables for VOMS
IMPORTANT NOTE!!: Updated documentation for the configuration of VOMS is now under https://twiki.cern.ch/twiki/bin/view/LCG/Site-info_configuration_variables#VOMS. These are all the necessary variables to configure VOMS. There are two example files coming in/opt/glite/yaim/examples/siteinfo. The site-info.def file, containing general variables and the services directory, containing the node type specific variables. Please, remember to move these files into your appropriate siteinfo directory where you store the YAIM configuration. You can also put all the variables together in the same file. For more details please check The configuration variables section in the YAIM guide.
Configuration variables for VOMS oracle
- Mandatory general variables: they can be found in
opt/glite/yaim/examples/site-info.defand they are described in the site-info.def variables section in the YAIM Guide:VOS.
- VOMS Oracle specific variables
- Mandatory variables: they can be found in
/opt/glite/yaim/examples/services/glite-voms_oracle. Sys admins must ensure these variables are properly defined according to the features of the site.
- Mandatory variables: they can be found in
| Variable Name | Description | Value type | Version |
VOMS_HOST |
hostname for the VOMS server | hostname | 1.0.0-3 |
VO_<vo-name>_VOMS_PORT |
The port on the VOMS server listening for request for each VO. This is used in the vomses configuration file. By convention, port numbers are allocated starting with 15000 | port number | 1.0.0-3 |
VO_<vo-name>_VOMS_DB_NAME |
Database name to be used to store VOMS information. Required on oracle installations, refers to the tns alias associated with the db. | DB name | 1.0.0-3 |
VO_<vo-name>_VOMS_DB_USER |
Name of the DB user | DB user name | 1.0.0-3 |
VO_<vo-name>_VOMS_DB_USER_PASSWORD |
Password of the DB user account | password | 1.0.0-3 |
VOMS_ADMIN_DB_HOST |
Hostname of the database server. Put 'localhost' if you run the database on the same machine. This parameter can be specified per VO in the following way: VO_<vo-name>_VOMS_ADMIN_DB_HOST |
hostname | 1.0.0-3 |
VOMS_ADMIN_SMTP_HOST |
Host to which voms-admin-service-generated emails should be submitted. Use 'localhost' if you have an fully configured SMTP server running on this host. Otherwise specify the hostname of a working SMTP submission service. This parameter can be specified per VO in the following way: VO_<vo-name>_VOMS_ADMIN_SMTP_HOST |
hostname | 1.0.0-3 |
VOMS_ADMIN_MAIL |
E-mail address that is used to send notification mails from the VOMS-admin. This parameter can be specified per VO in the following way: VO_<vo-name>_VOMS_ADMIN_MAIL |
1.0.0-3 |
-
- Optional variables: they can be found in
/opt/glite/yaim/examples/services/glite-voms_oracle. Sys admins just need to uncomment these variables if they want to define it for their site.
- Optional variables: they can be found in
| Variable Name | Description | Value type | Version |
VOMS_ADMIN_CERT |
The path of the certificate file (in pem format) of an initial VO administrator. The VO will be set up so that this user has full VO administration privileges. This parameter can be specified per VO in the following way: VO_<vo-name>_VOMS_ADMIN_CERT |
path | 1.0.0-3 |
VOMS_ADMIN_ORACLE_CONNECTION_STRING |
Specifies the oracle long connection string. Uncomment this variable if needed. Example: (DESCRIPTION= (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = lxfs5502.cern.ch)(PORT = 1521)) ) (CONNECT_DATA (SERVICE_NAME = egee102d.cern.ch)))This parameter can be specified per VO in the following way: =VO_<vo-name>_VOMS_ADMIN_ORACLE_CONNECTION_STRING |
oracle connection string | 1.0.0-3 |
VOMS_ADMIN_TOMCAT_GROUP |
The UNIX group that Tomcat is run under | group name | 1.0.0-3 |
VOMS_ADMIN_VOMS_GROUP |
The UNIX group that the VOMS core service is run under | group name | 1.0.0-3 |
-
- Default variables: sys admins don't need to change the value of these variables unless they know what they are doing. These variables have a meaningful default value provided by YAIM and can be found in
/opt/glite/yaim/defaults/glite-voms_oracle.pre and .post. Their value can be reset in your site-info.def file if necessary. Check the defaults directory section for more details.
- Default variables: sys admins don't need to change the value of these variables unless they know what they are doing. These variables have a meaningful default value provided by YAIM and can be found in
| Variable Name | Description | Value type | Default Value | Version |
VOMS_CORE_TIMEOUT |
The maximum length of validity of the ACs that VOMS will grant (in seconds) The default value is 24 hours This parameter can be specified per VO in the following way: VO_<vo-name>_VOMS_CORE_TIMEOUT |
seconds | 86400 |
1.0.0-3 |
VOMS_CORE_LOGROTATE_PERIOD |
This parameter can be specified per VO in the following way: VO_<vo-name>_VOMS_CORE_LOGROTATE_PERIOD |
daily, weekly, monthly | daily |
1.0.0-3 |
VOMS_CORE_LOGROTATE_LOGNUMBER |
This parameter can be specified per VO in the following way: VO_<vo-name>_VOMS_CORE_LOGROTATE_LOGNUMBER |
number of rotated log files | 90 |
1.0.0-3 |
VOMS_DB_TYPE |
DB type | oracle/mysql | oracle |
1.0.0-3 |
VOMS_ADMIN_INSTALL |
Set this variable to 'no' if you don't want to configure the voms-admin. | yes/no | yes |
1.0.0-3 |
VOMS_ADMIN_REQUEST_SCHEDULER |
Set this to 'yes' if you want to enable the build in request scheduler for voms admin. This parameter can be specified per VO in the following way: VO_<vo-name>_VOMS_ADMIN_REQUEST_SCHEDULER |
yes/no | no |
1.0.0-3 |
VOMS_ADMIN_WEB_REGISTRATION_DISABLE |
Set this variable to no if you want to disable the user registration via the voms-admin web interface. This parameter can be specified per VO in the following way: VO_<vo-name>_VOMS_ADMIN_WEB_REGISTRATION_DISABLE |
yes/no | yes |
1.0.0-3 |
VOMS_ADMIN_DEPLOY_DATABASE |
If set to 'yes' it will clean out and (re)create database schema. The current database contents will be lost. This parameter can be specified per VO in the following way: VO_<vo-name>_VOMS_ADMIN_DEPLOY_DATABASE |
yes/no | no |
1.0.0-3 |
VOMS_ADMIN_VERBOSE |
Verbosity | yes/no | yes |
1.0.0-3 |
VOMS_ADMIN_ORACLE_PORT |
Port number of the database server for oracle. This parameter can be specified per VO in the following way: VO_<vo-name>__ORACLE_PORT |
port number | 10121 |
1.0.0-3 |
VOMS_ADMIN_ORACLE_MIN_CONNECTIONS |
Minimum number of connections to be opened per VO | number | 1 |
1.0.0-3 |
VOMS_ADMIN_ORACLE_MAX_CONNECTIONS |
Maximum number of connections to be opened per VO | number | 20 |
1.0.0-3 |
VOMS_ADMIN_ORACLE_START_CONNECTIONS |
Startup number of connections to be opened per VO | number | 10 |
1.0.0-3 |
VOMS_ADMIN_ORACLE_CLIENT |
Location of the Oracle Instantclient installation | path | /usr/lib/oracle/10.2.0.1/client |
1.0.0-3 |
CATALINA_HOME |
Tomcat Catalina home directory | path | /var/lib/tomcat5 |
1.0.0-3 |
TOMCAT_USER |
Tomcat user name | user name | tomcat |
1.0.0-3 |
VOMS_ORACLE_LIBRARY |
Path to the oracle libraries | path | ${GLITE_LOCATION}/lib/libvomsoracle.so |
1.0.0-3 |
Topic revision: r6 - 2008-07-29 - MariaALANDESPRADILLO
LCG Wikis
- ABATBEA
- ACPP
- ADCgroup
- AEGIS
- AfricaMap
- AgileInfrastructure
- ALICE
- AliceEbyE
- AliceSPD
- AliceSSD
- AliceTOF
- AliFemto
- ALPHA
- Altair
- ArdaGrid
- ASACUSA
- AthenaFCalTBAna
- Atlas
- AtlasLBNL
- AXIALPET
- CAE
- CALICE
- CDS
- CENF
- CERNSearch
- CLIC
- Cloud
- CloudServices
- CMS
- Controls
- CTA
- CvmFS
- DB
- DefaultWeb
- DESgroup
- DPHEP
- DM-LHC
- DSSGroup
- EGEE
- EgeePtf
- ELFms
- EMI
- ETICS
- FIOgroup
- FlukaTeam
- Frontier
- Gaudi
- GeneratorServices
- GuidesInfo
- HardwareLabs
- HCC
- HEPIX
- ILCBDSColl
- ILCTPC
- IMWG
- Inspire
- IPv6
- IT
- ItCommTeam
- ITCoord
- ITdeptTechForum
- ITDRP
- ITGT
- ITSDC
- LAr
- LCG
- LCGAAWorkbook
- Leade
- LHCAccess
- LHCAtHome
- LHCb
- LHCgas
- LHCONE
- LHCOPN
- LinuxSupport
- Main
- Medipix
- Messaging
- MPGD
- NA49
- NA61
- NA62
- NTOF
- Openlab
- PDBService
- Persistency
- PESgroup
- Plugins
- PSAccess
- PSBUpgrade
- R2Eproject
- RCTF
- RD42
- RFCond12
- RFLowLevel
- ROXIE
- Sandbox
- SocialActivities
- SPI
- SRMDev
- SSM
- Student
- SuperComputing
- Support
- SwfCatalogue
- TMVA
- TOTEM
- TWiki
- UNOSAT
- Virtualization
- VOBox
- WITCH
- XTCA
 |
|
Copyright &© 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback