You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Burn Lewis (JIRA)" <de...@uima.apache.org> on 2016/02/18 15:19:18 UTC

[jira] [Resolved] (UIMA-4705) DUCC should provide the means for a security directory other than the user's home

     [ https://issues.apache.org/jira/browse/UIMA-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Burn Lewis resolved UIMA-4705.
------------------------------
    Resolution: Fixed

When in test mode must use real userid as the simulated use won't have a "security home"

> DUCC should provide the means for a security directory other than the user's home
> ---------------------------------------------------------------------------------
>
>                 Key: UIMA-4705
>                 URL: https://issues.apache.org/jira/browse/UIMA-4705
>             Project: UIMA
>          Issue Type: Improvement
>          Components: DUCC
>    Affects Versions: 2.0.1-Ducc
>            Reporter: Lou DeGenaro
>            Assignee: Burn Lewis
>             Fix For: 2.1.0-Ducc
>
>
> Problem:
> Presently DUCC uses public and private keys located in <user.home>/.ducc to ensure secure submissions.  On some clusters the usual home directory is not in the shared file system.
> Solution:
> In site.ducc.properties the administrator can optionally include a new specification.
> #
> # Location of security home directory.  
> # 
> # By default DUCC employs <user.home> as the user's security directory.
> # When ducc.security.home is specified here DUCC will instead employ
> # <ducc.security.home>/<user.name>.
> #
> #ducc.security.home = /users
> #



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)