From issues-return-12155-apmail-airavata-issues-archive=airavata.apache.org@airavata.apache.org Tue Sep 26 19:11:09 2017 Return-Path: X-Original-To: apmail-airavata-issues-archive@minotaur.apache.org Delivered-To: apmail-airavata-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5FF4E1075A for ; Tue, 26 Sep 2017 19:11:09 +0000 (UTC) Received: (qmail 56293 invoked by uid 500); 26 Sep 2017 19:11:04 -0000 Delivered-To: apmail-airavata-issues-archive@airavata.apache.org Received: (qmail 56263 invoked by uid 500); 26 Sep 2017 19:11:04 -0000 Mailing-List: contact issues-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@airavata.apache.org Received: (qmail 56246 invoked by uid 99); 26 Sep 2017 19:11:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Sep 2017 19:11:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 7836A182642 for ; Tue, 26 Sep 2017 19:11:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id fdtZeRskNTT7 for ; Tue, 26 Sep 2017 19:11:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 4D4EC61023 for ; Tue, 26 Sep 2017 19:11:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 744D3E0F62 for ; Tue, 26 Sep 2017 19:11:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 5F398242AB for ; Tue, 26 Sep 2017 19:11:00 +0000 (UTC) Date: Tue, 26 Sep 2017 19:11:00 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: issues@airavata.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AIRAVATA-2500) Automated cluster account provisioning for gateway users MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AIRAVATA-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16181354#comment-16181354 ] ASF subversion and git services commented on AIRAVATA-2500: ----------------------------------------------------------- Commit 277f34685da4273b1ee2f030b02c2830f6ca55e9 in airavata-php-gateway's branch refs/heads/develop from [~marcuschristie] [ https://git-wip-us.apache.org/repos/asf?p=airavata-php-gateway.git;h=277f346 ] AIRAVATA-2500 Prevent deleting in-use user credentials > Automated cluster account provisioning for gateway users > -------------------------------------------------------- > > Key: AIRAVATA-2500 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2500 > Project: Airavata > Issue Type: Bug > Components: Airavata System > Reporter: Marcus Christie > Assignee: Marcus Christie > > The initial use case for this system is the IU Cybergateway. We need the following capabilities: > * query for whether a user has an account > ** for IU Cybergateway the user cluster access is determined by querying LDAP > * add an SSH public key for the user to authenticate (actually Airavata to authenticate on behalf of the user) to the cluster > ** for IU Cybergateway the key is added to LDAP > Once the user has a cluster account and their SSH key has been added the following additional things need to be done > * test that Airavata can authenticate to the cluster on the users behalf > * add a scratch location that Airavata will use for the user on the cluster > Eric Coulter has developed a prototype LDAP client that can query for a user's account and deposit an SSH key in LDAP: https://github.iu.edu/jecoulte/airavata-ldap-prototype (note: this link is only accessible via IU credentials). -- This message was sent by Atlassian JIRA (v6.4.14#64029)