NameID are generated as I expect?

[Noriyuki TAKEI]

Hi,all.

I could solve this problem.

To add --sam2 option to aacli.sh allows me to get the result to distinct
NameID and attribute.

On Mon, Feb 18, 2019 at 12:52 PM Noriyuki TAKEI <ntakei at sios.com> wrote:

> Hi,All.
>
> I'd like to see whether the correct NameID and attributes I expected are
> generated before deployment to  production.
>
> In order to do this, I tried to use aacli.sh, but it seems that there is
> no differences in the result of aacli.sh between NameID and attributes.
>
> I got the following result, but I don't understand whether
> o365UserPrincipalName or  ImmutableID is the NameID.
>
> {
> "requester": "urn:federation:MicrosoftOnline",
> "principal": "test",
> "attributes": [
>
>
>   {
>     "name": "o365UserPrincipalName",
>     "values": [
>               "StringAttributeValue{value=test at example.com}"          ]
>   },
>
>   {
>     "name": "ImmutableID",
>     "values": [
>               "StringAttributeValue{value=test}"          ]
>   }
>
> ]
> }
>
> I'd like to let me know the way to know whether  NameID and attribute send
> exactly to SP or not before deployment to  production.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20190218/0e995867/attachment.html>