Before reporting an issue

[x] I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.

Area

docs

Describe the bug

The JSON-file example for the realm-attributes does contain legacy paramters that are no longer supported and lead to errors. The example looks like this:

{
  "realm": "oid4vc-vci",
  "enabled": true,
  "preAuthorizedCodeLifespanS": 120,
  "issuerDid": "https://localhost:8443/realms/oid4vc-vci",
  "attributes": {

"vc.IdentityCredential.expiry_in_s": "31536000",
"vc.IdentityCredential.format": "vc+sd-jwt",
"vc.IdentityCredential.scope": "identity_credential",
"vc.IdentityCredential.vct": "https://credentials.example.com/identity_credential",
"vc.SteuerberaterCredential.expiry_in_s": "31536000",
"vc.SteuerberaterCredential.format": "vc+sd-jwt",
"vc.SteuerberaterCredential.scope": "stbk_westfalen_lippe",
"vc.SteuerberaterCredential.vct": "stbk_westfalen_lippe",
"vc.SteuerberaterCredential.cryptographic_binding_methods_supported": "jwk"

  }
}

the attributes: preAuthorizedCodeLifespanS and issuerDid do not exist anymore.

—

The HTTP method for updating the realm is wrong: The curl example looks as follows:

curl -X POST "https://localhost:8443/admin/realms/oid4vc-vci" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d @realm-attributes.json

The HTTP method should be PUT instead of POST

Version

26.2.1

Regression

[ ] The issue is a regression

Expected behavior

-

Actual behavior

-

How to Reproduce?

-

Anything else?

No response