Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Docs: clarify reference to elytron-security-jdbc extension in the Security JDBC guide #37796

Merged
merged 1 commit into from
Dec 17, 2023
Merged

Docs: clarify reference to elytron-security-jdbc extension in the Security JDBC guide #37796

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/src/main/asciidoc/security-jdbc.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -184,8 +184,8 @@
[NOTE]
====
It is probably useless, but we kindly remind you that you must not store clear-text passwords in production environment ;-).
The `elytron-security-jdbc` offers a built-in bcrypt password mapper.
The `elytron-security-jdbc` extension offers a built-in bcrypt password mapper.
Please refer to the xref:security-getting-started-tutorial.adoc#define-the-user-entity[Define the user entity] section of the Getting Started with Security using Basic authentication and Jakarta Persistence tutorial for practical example.

Check warning on line 188 in docs/src/main/asciidoc/security-jdbc.adoc

View workflow job for this annotation

GitHub Actions / Linting with Vale 

[vale] reported by reviewdog 🐶
[Quarkus.TermsSuggestions] Depending on the context, consider using 'by using' or 'that uses' rather than 'using'.

Raw Output:
{"message": "[Quarkus.TermsSuggestions] Depending on the context, consider using 'by using' or 'that uses' rather than 'using'.", "location": {"path": "docs/src/main/asciidoc/security-jdbc.adoc", "range": {"start": {"line": 188, "column": 156}}}, "severity": "INFO"}
====

We can now configure the Elytron JDBC Realm.
Expand Down