[mo-auto]

Auto generated docs
Closes #15509,

Summary by CodeRabbit

• Documentation
  • Updated the API reference to reflect the current ordering of token details and FIDO2 metrics fields; their existing definitions and types are unchanged.
  • Added documented application configuration options for enabling security headers and applying them to responses based on URI contents.
  • Specified JAVA as the default crypto provider in the lock plugin schema.

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.

_{Tip: disable this comment in your organization's Code Review settings.}

[mo-auto]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

• Last reviewed commit: d1cdf5f
• Latest commit, not reviewed: 418b33a

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• Resume reviews
• Trigger review

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 03e3d526-cc43-423a-a8e2-b7e094d90ee2

Commits

Reviewing files that changed from the base of the PR and between 180f1f5 and d1cdf5f.

Files selected for processing: 1

• jans-config-api/plugins/docs/fido2-plugin-swagger.yaml

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.

Walkthrough

The Config API Swagger schema adds two security header properties and reorders properties in two schemas. The FIDO2 plugin Swagger schema reorders metrics properties. The lock plugin Swagger schema sets JAVA as the default for cryptoProvider.

Changes: Swagger schema updates

Layer / File(s)	Summary
Update Config API schemas jans-config-api/docs/jans-config-api-swagger.yaml	AppConfiguration adds securityHeadersEnabled and applySecurityHeadersIfUriContainsAny. JansAttribute and TokenEntity properties are reordered; their types remain unchanged.
Reorder FIDO2 metrics properties jans-config-api/plugins/docs/fido2-plugin-swagger.yaml	Fido2MetricsAggregation properties are reordered. Their definitions remain unchanged.
Set crypto provider default jans-config-api/plugins/docs/lock-plugin-swagger.yaml	TraceConfiguration.cryptoProvider now declares JAVA as its default.

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Possibly related PRs

• JanssenProject/jans#15476: This PR also updates generated Swagger declarations, including FIDO2 metrics properties and the cryptoProvider default.
• JanssenProject/jans#15499: This PR overlaps the JansAttribute, TokenEntity, and TraceConfiguration.cryptoProvider declarations.
• JanssenProject/jans#15515: This PR adds runtime AppConfiguration properties that this PR documents in the Swagger schema.

Suggested labels: comp-jans-config-api, comp-docs, area-documentation, comp-jans-fido2, comp-jans-lock

Merge Risk: Minimal · previous review d1cdf

The Swagger updates are consistent with the implemented configuration behavior and introduce no verified merge-blocking risk.

Pre-merge checks: 4 · 1

Failed checks: 1 warning

Check name	Status	Explanation	Resolution
Description check		The description states that the documentation was autogenerated and references issue #15509. It omits the required preparation checklist, implementation details, test results, documentation checklist,…	Complete the PR description template. Add the target issue in the required format, implementation details, test and static analysis results, documentation impact, and all applicable checklist selections.

Passed checks: 4 passed

Check name	Status	Explanation
Title check		The title clearly identifies the main change: autogenerated documentation updates.
Linked Issues check		Issue #15509 is open and directly linked. The issue only states that PR #15508 lacked an open issue reference. It defines no coding requirement or acceptance criterion. No linked-issue coding requirem…
Out of Scope Changes check		The changes are limited to autogenerated Swagger documentation. They reorder schema properties, add two AppConfiguration properties, and set the TraceConfiguration.cryptoProvider default to JAVA…
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…

Full details: Linked Issues check

Explanation

Issue #15509 is open and directly linked. The issue only states that PR #15508 lacked an open issue reference. It defines no coding requirement or acceptance criterion. No linked-issue coding requirement applies.

Full details: Out of Scope Changes check

Explanation

The changes are limited to autogenerated Swagger documentation. They reorder schema properties, add two AppConfiguration properties, and set the TraceConfiguration.cryptoProvider default to JAVA. These changes match the current PR intent, Auto generated docs. No unrelated change is shown.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

Full details: Description check

Explanation

The description states that the documentation was autogenerated and references issue #15509. It omits the required preparation checklist, implementation details, test results, documentation checklist, and confirmation of the final PR checks.

Resolution

Complete the PR description template. Add the target issue in the required format, implementation details, test and static analysis results, documentation impact, and all applicable checklist selections.

Finishing Touches

Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[mo-auto]

Error: Hi @mo-auto, You did not reference an open issue in your PR. I attempted to create an issue for you.
Please update that issues' title and body and make sure I correctly referenced it in the above PRs body.

[sonarqubecloud]

Quality Gate passed for 'jans-config-api-parent'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud