NLB-6926: Update NGINXaaS docs with R35 changelog #1142
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
documentation
Naveen-Gopu-F5
force-pushed
the
NLB-6929-docs-update-for-r35
branch
from
097d16e to
34fdc03
Compare
y82
approved these changes
Sep 24, 2025
content/nginxaas-azure/changelog.md
Outdated
| - nginx-plus-module-njs | ||
| For a complete list of allowed directives, see the [Configuration Directives List]({{< ref "/nginxaas-azure/getting-started/nginx-configuration/overview/#configuration-directives-list" >}}). | ||
|
|
||
| The ACME protocol support feature, available in NGINX Plus R35, is not currently supported in NGINXaaS due to active-active deployments. |
There was a problem hiding this comment.
Suggested change
| The ACME protocol support feature, available in NGINX Plus R35, is not currently supported in NGINXaaS due to active-active deployments. | |
| The [ACME protocol support](https://nginx.org/en/docs/http/ngx_http_acme_module.html) feature, available in NGINX Plus R35 as a [dynamic module]({{< ref "/nginx/admin-guide/dynamic-modules/acme.md" >}}), is not currently supported in NGINXaaS due to active-active deployments. |
There was a problem hiding this comment.
applied suggest changes
content/nginxaas-azure/changelog.md
Outdated
|
|
||
| - {{% icon-feature %}} **NGINXaaS is now running NGINX Plus Release 35 (R35) in the Stable Upgrade Channel** | ||
|
|
||
| NGINXaaS for Azure deployments using the **Stable** [Upgrade Channel]({{< ref "/nginxaas-azure/quickstart/upgrade-channels.md" >}}) have now been automatically upgraded to [NGINX Plus Release 35 (R35)]({{< ref "/nginx/releases.md#nginxplusrelease-35-r35" >}}). This upgrade also includes updates to the following NGINX Plus modules: |
There was a problem hiding this comment.
Suggested change
| NGINXaaS for Azure deployments using the **Stable** [Upgrade Channel]({{< ref "/nginxaas-azure/quickstart/upgrade-channels.md" >}}) have now been automatically upgraded to [NGINX Plus Release 35 (R35)]({{< ref "/nginx/releases.md#nginxplusrelease-35-r35" >}}). This upgrade also includes updates to the following NGINX Plus modules: | |
| NGINXaaS for Azure deployments using the **Stable** [Upgrade Channel]({{< ref "/nginxaas-azure/quickstart/upgrade-channels.md" >}}) have now been automatically upgraded to [NGINX Plus Release 35 (R35)]({{< ref "/nginx/releases.md#nginxplusrelease-35-r35" >}}). This upgrade also includes updates to the following NGINX Plus modules: |
There was a problem hiding this comment.
applied suggest changes
content/nginxaas-azure/changelog.md
Outdated
| - {{% icon-feature %}} **NGINXaaS is now running NGINX Plus Release 35 (R35) in the Stable Upgrade Channel** | ||
|
|
||
| NGINXaaS for Azure deployments using the **Stable** [Upgrade Channel]({{< ref "/nginxaas-azure/quickstart/upgrade-channels.md" >}}) have now been automatically upgraded to [NGINX Plus Release 35 (R35)]({{< ref "/nginx/releases.md#nginxplusrelease-35-r35" >}}). This upgrade also includes updates to the following NGINX Plus modules: | ||
| - nginx-plus-module-njs |
There was a problem hiding this comment.
Suggested change
| - nginx-plus-module-njs | |
| - `nginx-plus-module-njs` |
There was a problem hiding this comment.
applied suggest changes
| This is a site protected by OIDC! | ||
| ``` | ||
| There is another method to set up OIDC authentication using the native OIDC module, which can be tried out as an experimental method using [this process](https://github.com/nginxinc/nginxaas-for-azure-snippets/tree/main/terraform/configurations/native-oidc). We recommend using the above method, which uses the njs module. |
There was a problem hiding this comment.
Suggested change
| There is another method to set up OIDC authentication using the native OIDC module, which can be tried out as an experimental method using [this process](https://github.com/nginxinc/nginxaas-for-azure-snippets/tree/main/terraform/configurations/native-oidc). We recommend using the above method, which uses the njs module. | |
| There is another method to set up OIDC authentication using the [native OIDC module](https://nginx.org/en/docs/http/ngx_http_oidc_module.html), which can be tried out as an experimental method using [this process](https://github.com/nginxinc/nginxaas-for-azure-snippets/tree/main/terraform/configurations/native-oidc). We recommend using the above method, which uses the njs module. |
There was a problem hiding this comment.
These implementations are different: nginx native OIDC module vs njs-based OIDC.
Native OIDC module appeared in R34, while njs-based OIDC was available before (pls see this blogpost)
There was a problem hiding this comment.
Raised a separate PR to update Native OIDC docs
russokj
approved these changes
Sep 25, 2025
Naveen-Gopu-F5
force-pushed
the
NLB-6929-docs-update-for-r35
branch
from
34fdc03 to
e2a6863
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩