[Declarative User Profile] Attributes are created as required by default but switch is set to "not required"

[jbman]

Before reporting an issue

• I have searched existing issues
• I have reproduced the issue with the latest release

Area

user-profile

Describe the bug

When declaring a new attribute with "required" switch "off", the attribute is required after saving.

Version

21.1.1

Expected behavior

The attribute should be stored as not required

Actual behavior

The attribute is stored as required, although switch is set to off and isn't toggled.

How to Reproduce?

Create an attribute with just a name and save.

Open the attribute and see that it is required now.

Anything else?

Workaround: When you know the bug, you can open the attribute and correct the setting. If not known, it is a surprise that user's can't be created any more without a value for the attribute.

[jbman]

Also the fine grained required settings seem to be broken:
"Required when" is set to "Always" but there are scopes listed in the JSON representation.

Stored as:

{
        ...,
	"required": {
		"roles": [
			"admin",
			"user"
		],
		"scopes": [
			"role_list",
			"profile",
			"email",
			"acr",
			"microprofile-jwt",
			"offline_access",
			"phone",
			"address",
			"roles",
			"web-origins"
		]
	}
}

[mposolda]

@jbman Thanks for the report. I am adding to Backlog for now. We may need to revisit if we want to make user-profile to be supported feature.

[pedroigor]

Thanks. The behavior looks correct and fixed in both the latest release (22.0.4) and upstream/main.