Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9DB441726E for ; Thu, 4 Jun 2015 22:18:38 +0000 (UTC) Received: (qmail 50698 invoked by uid 500); 4 Jun 2015 22:18:38 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 50663 invoked by uid 500); 4 Jun 2015 22:18:38 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 50653 invoked by uid 500); 4 Jun 2015 22:18:38 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 50650 invoked by uid 99); 4 Jun 2015 22:18:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Jun 2015 22:18:38 +0000 Date: Thu, 4 Jun 2015 22:18:38 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-8457) Make SAML plugin production grade 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/CLOUDSTACK-8457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573685#comment-14573685 ] ASF subversion and git services commented on CLOUDSTACK-8457: ------------------------------------------------------------- Commit 001237312739babb99f025d29a99c9b6616e5365 in cloudstack's branch refs/heads/saml-production-grade from [~rohit.yadav@shapeblue.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0012373 ] CLOUDSTACK-8457: add a default set of SAML SP cert for testing purposes Now to enable and use saml, one needs to do a deploydb-saml after doing a deploydb Signed-off-by: Rohit Yadav > Make SAML plugin production grade > --------------------------------- > > Key: CLOUDSTACK-8457 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8457 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the default.) > Components: SAML > Reporter: Rohit Yadav > Assignee: Rohit Yadav > Fix For: Future, 4.6.0, 4.5.2 > > > The current SAML plugin is not well tested with major IdPs used in production such as Shibboleth. It is also limited to using HTTP-redirect only and does not support HTTP-Post and other artifacts. Further, the security concerns are not well addressed, for example both authorization, creation of users/accounts (on first login) and authentication is done by the plugin which needs to be tested wrt security, addressed and improved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)