Description
The UST Action Summary reports a "new Adobe user(s) added" when a given email ID is marked for Federated ID creation even if it then gets skipped because an Adobe ID is already associated with that email ID.
Steps to reproduce
Relevant config options
I used all default configuration options.
Command-line options used
No extra CLI options used.
Specific details around identity source, group mapping, etc.
At least one member of a directory group selected for input should have an email address that already has an Adobe ID associated with it on the target Admin Console. I used a CSV input, but the specific identity source doesn't matter here.
Expected behavior
In this case, since the Federated ID creation gets skipped over because of the preexisting Adobe ID, the UST Action Summary should not report that a new Adobe user was added.
Screenshots
Here is the CSV file input I used for this user:
Here is the target Admin Console showing an Adobe ID already associated with the email adobe3@seaofcarag.com:
And here is the resulting output and action summary:
The action summary reports 1 new Adobe user added, yet there were no UMAPI actions sent and no user was in fact created on this run, so it should say 0. This has caused confusion for at least one customer as they parse through their UST action summaries.
Description The UST Action Summary reports a "new Adobe user(s) added" when a given email ID is marked for Federated ID creation even if it then gets skipped because an Adobe ID is already associated with that email ID. Steps to reproduce
Expected behavior In this case, since the Federated ID creation gets skipped over because of the preexisting Adobe ID, the UST Action Summary should not report that a new Adobe user was added.
Screenshots Here is the CSV file input I used for this user:
Here is the target Admin Console showing an Adobe ID already associated with the email adobe3@seaofcarag.com:
And here is the resulting output and action summary:
The action summary reports 1 new Adobe user added, yet there were no UMAPI actions sent and no user was in fact created on this run, so it should say 0. This has caused confusion for at least one customer as they parse through their UST action summaries.
Environment