shibboleth SP generating two values for attributes from azure

[Sean Flannery]

Thanks, Scott.

I can't think of anything that's leveraging the alias feature.  That said:


1) I was able to solve our problem by using the exportDuplicateValues="false" feature of RequestMap so we are good now.


2) I did notice in the transaction log that each attribute is being processed twice- I would think that's why its duplicated.


I missed the second occurrence in logs yesterday.  Not sure if that would mean anything to anyone.

The transaction log looks something like this:


2018-11-05 19:14:33|Shibboleth-TRANSACTION|Cached the following attributes with session (ID: _b3f8ea8e8f86df25b6af513ebc2f142d) for (applicationId: default) {
2018-11-05 19:14:33|Shibboleth-TRANSACTION| email (1 values)
2018-11-05 19:14:33|Shibboleth-TRANSACTION| cn (1 values)
...  more attributes, then-
2018-11-05 19:14:33|Shibboleth-TRANSACTION| email (1 values)
2018-11-05 19:14:33|Shibboleth-TRANSACTION| cn (1 values)

So each of the attributes coming back from Azure seem to be processed twice in transaction.log

Again, problem is solved through exportDuplicateValues so not really an issue anymore but if anyone might understand what issue/misconfiguration causes the azure attributes to be processed twice, it would be nice to fix the core issue if possible.

Thanks for your time.

Sean


________________________________
From: users <users-bounces at shibboleth.net> on behalf of Cantor, Scott <cantor.2 at osu.edu>
Sent: Monday, November 5, 2018 1:42:49 PM
To: Shib Users
Subject: RE: shibboleth SP generating two values for attributes from azure

The alias feature in the attribute mapping rules is about the only thing that comes to mind, that or an application issue.

-- Scott

--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20181106/54b4c928/attachment.html>