Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Received-SPF: pass (nike.apache.org: domain of rlevas@hortonworks.com
 designates 209.85.216.169 as permitted sender)
From: Robert Levas <rlevas@hortonworks.com>
Subject: [DISCUSS] Session data made available to API resource handlers
Message-Id: <4C4EA29A-D9AE-44E0-915E-07AA28EC5E47@hortonworks.com>
Date: Mon, 24 Nov 2014 09:30:00 -0500
To: Ambari <dev@ambari.apache.org>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_94AC2F18-D4FE-43C6-81BD-7D13F2504792"

--Apple-Mail=_94AC2F18-D4FE-43C6-81BD-7D13F2504792
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=windows-1252

Team=85

I thought that this might be an interesting topic to discuss. =20

I am looking at a situation where it would be nice to have a dynamically ge=
nerated encryption key stored in a web server session.  This key could be u=
sed to encrypt sensitive data that needs to be shared across REST API calls=
 during that session.   In the JIRA that I created for this - https://issue=
s.apache.org/jira/browse/AMBARI-8426 - I propose a use-case related to the =
automation of enabling (or disabling) Kerberos in a cluster.=20

If we take the more generate route that is proposed in the JIRA, we could p=
ossibly do other things by storing data in the session - not just the encry=
ption facility I need.  However I would be happy to just have the encryptio=
n key if we wanted to limit the scope of access to session data across REST=
 API calls.

Please take a look and provide feedback or suggestions for alternative ways=
 I might accomplish this.  Since this is needed to the upcoming 2.0.0 relea=
se, I would like to have something in the works by Wednesday.=20

Thanks,

Rob


--=20
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to=
=20
which it is addressed and may contain information that is confidential,=20
privileged and exempt from disclosure under applicable law. If the reader=
=20
of this message is not the intended recipient, you are hereby notified that=
=20
any printing, copying, dissemination, distribution, disclosure or=20
forwarding of this communication is strictly prohibited. If you have=20
received this communication in error, please contact the sender immediately=
=20
and delete it from your system. Thank You.

--Apple-Mail=_94AC2F18-D4FE-43C6-81BD-7D13F2504792--