Software Links
Getting Started
- Doc Structure
- A Globus Primer
- Globus Is Modular!
- Quickstart
- Installing GT
- Platform Notes
- Migrating from GT2
- Migrating from GT3
Reference
- PDF version
- Best Practices
- Coding Guidelines
- API docs
- Public Interfaces
- Resource Properties
- Samples
- Glossary
- Performance Studies
Common Runtime
Security
Data Mgt
Information Svcs
Execution Mgt
Name
cas-group-add-entry — Adds CAS objects to CAS groups
Synopsis
cas-group-add-entry [common options] user groupName nickname cas-group-add-entry [common options] object groupName objectSpecDesc objectSpec cas-group-add-entry [common options] serviceAction groupName serviceTypeName actionName
Tool description
Use cas-group-add-entry to add users to a user group, objects to an object group, or service/actions to service/action groups. Note: to add or delete groups, see [link to other clients].
Adding Member To A User Group
To add a user to a user group, the user must have cas/add_group_entry permission on that particular user group. Only user nicknames that exist in the CAS database can be valid members.
casAdmin$cas-group-add-entry [common options] usergroupNamenickname
where:
-
groupName - Indicates the user group name to which the member needs to be added.
-
nickname - Indicates the nickname of the user to be added to this group.
Adding Member To An Object Group
To add a member (an object group can have the following CasObjects as members: object, user, user group, service type, namespace or trust anchor) to an object group, the user must have cas/add_group_entry permission on that particular object group.
casAdmin$cas-group-add-entry [common options] objectgroupNameobjectSpecDescobjectSpec
where:
-
groupName - Indicates the object group name to which the member needs to be added.
-
objectSpecDesc Indicates the type of CasObject. Can be one of the following options:
trustAnchoruseruserGroupobjectnamespaceserviceType
-
objectSpec Indicates the identifier for the CasObject the user is adding. Can be one of the following:
nicknameif adding a trustAnchor or usergroupNameif adding a userGroupobjectNamespaceobjectName if adding an objectnicknameif adding a namespaceserviceTypeNameif adding a serviceType
Adding Service/Action To A Service/Action Group
To add a service/action to a serviceAction group, the user must have cas/add_group_entry permission on that particular serviceAction group (that is, the user must have permission to perform add_group_entry action on that service action group).
casAdmin$cas-group-add-entry [common options] serviceActiongroupNameserviceTypeNameactionName
where:
-
groupName - Indicates the service/action group to which the service/action needs to be added.
-
serviceTypeName - Indicates the service type name part of the mapping to be added to the group.
-
actionName - Indicates the action name part of the mapping to be added to the group.
Options
- -a, --anonymous
Enables anonymous authentication. Only supported with transport security or the GSI Secure Conversation authentication mechanism.
- -c, --serverCertificate
<file> Specifies the server's certificate file used for encryption. Only needed for the GSI Secure Message authentication mechanism.
- -debug
Runs the client with debug message traces and error stack traces.
- -f, --descriptor
<file> Specifies a client security descriptor. Overrides all other security settings.
- -help
Prints the usage message for the client.
- -l, --contextLifetime
<value> Sets the lifetime of the client security context.
valueis in milliseconds. Only supported with the GSI Secure Conversation authentication mechanism [FIXME glossterm?].- -m, --securityMech
<type> Specifies the authentication mechanism. The value
typecan be:msgfor GSI Secure Message, orconvfor GSI Secure Conversation.
- -p, --protection
<type> Specifies the protection level.
typecan be:sigfor signature, orencfor encryption.
- -x, --proxyFilename
<value> Sets the proxy file to use as client credential.
- -s
cas-url Sets the CAS Service instance, where
cas-urlis the URL of the CAS service instance. Alternatively, an environment variable can be set as shown here.The instance URL typically looks like
http://Host:Port/wsrf/services/CASService, whereHostandPortare the host and port where the container with the CAS service is running.- -z
authorization Specifies the type of authorization used, such as
selforhost.If you cannot use a standard method for authorization, you can use the specific CAS server's identity as the value.
Alternatively, an environment variable can be set as shown here.
If none of the above are set, host authorization is done by default and the expected server credential is
cas/, where<fqdn><fqdn>is the fully qualified domain name of the host on which the CAS service is up.![[Note]](/docbook-images/note.gif)
Note If the service being contacted is using GSI Secure Transport [FIXME glossterm], then the container credentials configured for the service will be used, even if service/resource level credentials are configured. Hence authorization needs to be done based on the DN of the container credentials.
- -v
Prints the version number.
![]() | Important |
|---|---|
If you have an asterisk (*) in your command, you might need to escape it with a backslash ( \ ). |
![[Important]](/docbook-images/important.gif)