SAP IAS/IPS - Email condition to restrict provisioning of users with dummy mail adresses

[LutzLimbach]

Hi all,

we have to provision Users from SuccessFactors to IAS and SAC.

But we have some dummy-users (with mail-adress *@dummy.sap.com) which we don't want to push to IAS/SAC.

We tried quite some time with different conditions, but still didn't find the correct syntax.

These are our last tries:

"condition": "$.emails[0].length() > 0 || ($.emails[0].value =~ /^((?!@dummy.sap.com).)*$/)",

"condition": "$.emails[0].length() > 0 && ($.emails[0].value =~ /^((?!@dummy.sap.com).)*$/)",
"condition": "$.emails[0].length() > 0 || ($.emails[0].value =~ /(?!@dummy.sap.com)/)",

Simulation jobs with any of these conditions will create all users with a mail adress, throw errors for users without a mail adress but doesn't filter these with *@dummy.sap.com.

Any ideas where the problem with the syntax to filter out users these dummy addresses lies?

Best Regards

Lutz

[MSo]

Sorry for that Lutz, I was not aware of a potential authorization issue.

Let me quote the example given in the blog (I don't have copyright for this, it's just copy&pasted...):

The syntax for the regular expressions is as follows:

"The template for such a condition is the following:

"condition": "$.<attribute> =~ /.*<text>.*/",

=~ means that a regular expression (regex) will be tested in the condition

/ represents the start and end of the regex

.* represents any symbol

<text> is a placeholder for the string that you want the value to contain"

Example: Check if the first email address of a user contains a particular domain:

"condition": "$.emails[0].value =~ /.*@example.com/",

Sample for an IAS target transformation given by Chris Paine to exclude users with certain dummy email addresses

{
"user": {
"condition": "($.emails.length() > 0) && ($.name.familyName EMPTY false) && ($.emails[0].value != 'dummy@sap.com') && ($.emails[0].value != 'no-one@nomail.com') && ($.emails[0].value != 'nomail@nomail.com')",
"mappings": [
{
...

[willianlima]

Dear Marko,

Do you have an example on how to avoid sending messages on create to SSO users ?

Kind regards,

Willian Lima