You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow
7
-
readme: |
8
-
<p>The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow</p>
9
-
<ul>
10
-
<li>Point of contact: @sberyozkin (@_<strong>Sergey Beryozkin</strong> on Zulip)</li>
In the past month, the WG - OIDC improvements has successfully closed an issue focused on providing migration guides for transitioning from Vert.x OIDC to Quarkus OIDC, enhancing the usability of the framework. No new issues were opened during this period, indicating a focus on completing existing tasks and improving the overall OIDC experience.
21
-
22
-
(This status update was automatically generated using AI.)
23
-
deliverable: TBD
24
-
point-of-contact: "@sberyozkin (@_<strong>Sergey Beryozkin</strong> on Zulip)"
In the last month, the WG - Dev Services Lifecycle has made significant progress by closing several issues related to the Redis dev services, including enhancements in testing and controlling their startup behavior during augmentation. Additionally, new issues were opened to refine test coverage further and simplify the development services model, indicating ongoing efforts to enhance the developer experience and consistency.
@@ -52,6 +29,29 @@ working-groups:
52
29
point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong> on Zulip), @ozangunalp (@<strong>Ozan Günalp</strong> on Zulip )"
The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow
36
+
readme: |
37
+
<p>The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow</p>
38
+
<ul>
39
+
<li>Point of contact: @sberyozkin (@_<strong>Sergey Beryozkin</strong> on Zulip)</li>
In the past month, the WG - OIDC improvements has successfully closed an issue focused on providing migration guides for transitioning from Vert.x OIDC to Quarkus OIDC, enhancing the usability of the framework. No new issues were opened during this period, indicating a focus on completing existing tasks and improving the overall OIDC experience.
50
+
51
+
(This status update was automatically generated using AI.)
52
+
deliverable: TBD
53
+
point-of-contact: "@sberyozkin (@_<strong>Sergey Beryozkin</strong> on Zulip)"
0 commit comments