After saving custom oauth property mapping, it remains "managed" and no default re-created

[patschi]

Describe the bug

When editing a default object and saving it, typically it gets "special-handled" to cause the blueprint to re-create the default and leaving the now-custom object untouched. I'd expect the same for Property Mappings, however it doesn't seem to behave the same way.

When deciding to have Hide managed mappings enabled, I can see following profile mapping:

But when disabling it, I can see my custom (previously default mapping) again:

So it appears that the mapping is still seen as as a managed item, but I'd not expect it to.

I have indeed customized it too:

How to reproduce

1. Go Property Mappings
2. Edit default property mapping and save it
3. It will be saved as expected, but still seen as managed item
4. When running blueprint, any own changes will be forced and my custom object is 'deleted'

Expected behavior

The object not to be considered 'managed' and not overwritten when running blueprint.

Screenshots

No response

Additional context

No response

Deployment Method

Docker

Version

2025.10.3

Relevant log output