AWS AppStream

[Yavor Yanakiev]

We, at NYU, launched recently  WAS AppStream pilot project, but we do not
use  LDAP, not AD.
Persistent ID needs to be opeque ad thus, you can use userPrincipalName as
a source to calculate the value but not as a value.


On Fri, Aug 4, 2017 at 10:18 AM, Hong Ye <hy93 at cornell.edu> wrote:

> Hello,
>
>
>
> Has anyone integrated AWS AppStream with Shibboleth IDP 3? In AWS
> document, it has a note say ‘For stacks with domain-joined fleets, the
> NameID for the user must be provided in the format of "domain\username"
> using the sAMAccountName or "username at domain.com" using
> userPrincipalName. If using the sAMAccountName format, the domain can be
> specified using either the NetBIOS name or the fully qualified domain name
> (FQDN).’
>
>
>
> According to AWS’s metadata(https://signin.aws.amazon.com/static/saml-
> metadata.xml), it requires nameID format:
>
> <NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:
> transient</NameIDFormat>
>
> <NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:
> persistent</NameIDFormat>
>
>
>
> Is it possible to use userPrincipalName as the value of persistentID just
> for AWS?
>
>
>
> Thanks,
>
> Hong
>
>
>
>
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>



-- 
Yavor Yanakiev
Systems Developer for Identity Services
212-992-7585
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170804/43f0ef03/attachment.html>