Active state gets saved incorrectly in jackson_store for Directory sync

[Christophvh]

Active state gets saved incorrectly in jackson_store for Directory sync

[devkiran]

Thank you for bringing this issue to our attention. We'll try to reproduce this issue and get back to you.

[devkiran]

Please ensure that the directory connection type is set to azure-scim-v2. To comply with the SCIM 2.0 standard, it is necessary to append ?aadOptscim062020 to the SCIM URL.

For example api/scim/v2.0/876394bf-d131-4dba-bfcd-48f6bb9f5cb9/?aadOptscim062020

const { data, error } = await directorySync.directories.create({
  name: "Azure AD",
  tenant: "your-tenant-id",
  product: "your-product-id",
  type: "azure-scim-v2", // <-- this is the important part
});

[Christophvh]

The type is set correctly. But never seen any mention about the '?aadOptscim062020' part. Should this be added in the jackson store too? Or should we add this to the Azure portal? This should be done by default in the DB if it's that important.

DB:

[devkiran]

Yeah, it is not there in the database yet. We'll think about it.

You'll get it when you call directories.get() method.

{
  data: {
    id: '876394bf-d131-4dba-bfcd-48f6bb9f5cb9',
    name: 'Azure',
    tenant: 'boxyhq1',
    product: 'demo',
    type: 'azure-scim-v2',
    log_webhook_events: false,
    scim: {
      path: '/api/scim/v2.0/876394bf-d131-4dba-bfcd-48f6bb9f5cb9/?aadOptscim062020',
      secret: 'l61O_0ZSjAHbLc5bXZpbdw',
      endpoint: 'http://localhost:5225/api/scim/v2.0/876394bf-d131-4dba-bfcd-48f6bb9f5cb9/?aadOptscim062020'
    },
    deactivated: false
  },
  error: null
}

In your case you can append /?aadOptscim062020 directly to SCIM endpoint in the Azure portal.

[Christophvh]

I added this to the Azure Portal, but got the same error when doing the scenario provided in my initial question. Also 'False' is still set as a string instead of a boolean.

So it seems like the '?' parameter does not change anything.

[devkiran]

Can you try removing the user from the database and add again? I think it is because of the user already exists in the database with active = "False".

[Christophvh]

Can you try removing the user from the database and add again? I think it is because of the user already exists in the database with active = "False".

I did this. I fully cleared my DB and reran all provisions.

[devkiran]

I can look into your setup if the changes doesn't work. Can you DM me on our discord channel https://discord.gg/uyb7pYt4Pa

[devkiran]

This could be related to this issue: #1472

[devkiran]

Feel free to reopen if this issue still exists.