Sync documentation of main branch

Author: actions-user

_generated-doc/main/infra/quarkus-all-build-items.adoc

@@ -7223,7 +7223,11 @@ a| https://github.com/quarkusio/quarkus/blob/main/extensions/resteasy-reactive/r
 [.description]
 --
 Represents a JAX-RS resource that is generated. Meant to be used by extension that generate JAX-RS resources as part of their build time processing
--- a|`java.lang.String name` 
+-- a|`java.lang.String binaryName` 
+
+_No Javadoc found_
+
+`java.lang.String internalName` 
 
 _No Javadoc found_
 

_versions/main/guides/flyway.adoc

@@ -448,3 +448,27 @@ quarkus.openshift.init-task-defaults.wait-for-container.image=my/wait-for-image:
 ----
 
 **Note**: In this context globally means `for all extensions that support init task externalization`.
+
+== Known Issues in Flyway
+
+=== Oracle: Multiple schemas in Dev Services
+
+When having multiple schemas in Oracle, you can use the `quarkus.flyway.schemas` property to specify the schemas that Flyway should manage.
+However, because this is executed in the DB as the `quarkus` user, you need to either give DBA privileges to the user that is executing the migration (`quarkus`) or perform the necessary DDLs before the Dev Service starts. This is done with the `quarkus.datasource.devservices.init-script-path` configuration.
+
+==== Giving DBA privileges to the user
+
+- In your application, create a SQL file named `001-devservice-init.sql` (for ordering purposes, it can be any name really) in your `src/main/resources` with the following content:
+
+[source,sql]
+----
+ALTER SESSION SET CONTAINER=quarkus;
+GRANT DBA TO quarkus;
+----
+
+- Add the following configuration to your `application.properties`:
+
+[source,properties]
+----
+quarkus.datasource.devservices.init-script-path=001-devservice-init.sql
+----

_versions/main/guides/security-openid-connect-providers.adoc

@@ -230,6 +230,21 @@ quarkus.oidc.client-id=<Client ID>
 quarkus.oidc.credentials.secret=<Secret>
 ----
 
+[NOTE]
+====
+By default, Quarkus GitHub provider submits the client id and secret in the HTTP Authorization header.
+However, GitHub may require that both client id and secret are submitted as form parameters instead.
+When you get HTTP 401 error after logging in to GitHub and being redirected back to Quarkus MCP server,
+replace the `quarkus.oidc.credentials.secret=<Secret>` property
+with the following two properties instead:
+
+[source,properties]
+----
+quarkus.oidc.credentials.client-secret.method=post
+quarkus.oidc.credentials.client-secret.value=<Secret>
+----
+====
+
 `quarkus.oidc.provider=github` will request GitHub to add a `user:email` scope to issued access tokens. For information about overriding this scope or requesting more scopes, see the  <<provider-scope>> section.
 
 TIP: You can also send access tokens issued by GitHub to `quarkus.oidc.application-type=service` or `quarkus.oidc.application-type=hybrid` Quarkus applications.