diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-05-25 23:30:46 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-05-25 23:30:46 +0300 |
commit | 1d287b31040662f1cc53a61b866ea97931a6b850 (patch) | |
tree | 64c1ff71f40695c1d516a7b24cabf06c408685f1 /doc/api | |
parent | fdcb3d47df0526a9dc437c847683df8aae1e5d58 (diff) |
Add latest changes from gitlab-org/gitlab@13-12-stable-ee
Diffstat (limited to 'doc/api')
-rw-r--r-- | doc/api/groups.md | 27 | ||||
-rw-r--r-- | doc/api/oauth2.md | 6 |
2 files changed, 20 insertions, 13 deletions
diff --git a/doc/api/groups.md b/doc/api/groups.md index cbead18ff90..6bec6e0f6f8 100644 --- a/doc/api/groups.md +++ b/doc/api/groups.md @@ -722,18 +722,21 @@ Example response: } ``` -### Disabling the results limit +### Disable the results limit **(FREE SELF)** -The 100 results limit can be disabled if it breaks integrations developed using GitLab -12.4 and earlier. +The 100 results limit can break integrations developed using GitLab 12.4 and earlier. -To disable the limit while migrating to using the [list a group's projects](#list-a-groups-projects) endpoint, ask a GitLab administrator -with Rails console access to run the following command: +For GitLab 12.5 to GitLab 13.12, the limit can be disabled while migrating to using the +[list a group's projects](#list-a-groups-projects) endpoint. + +Ask a GitLab administrator with Rails console access to run the following command: ```ruby Feature.disable(:limit_projects_in_groups_api) ``` +For GitLab 14.0 and later, the [limit cannot be disabled](https://gitlab.com/gitlab-org/gitlab/-/issues/257829). + ## New group Creates a new project group. Available only for users who can create groups. @@ -918,19 +921,21 @@ Example response: } ``` -### Disabling the results limit +### Disable the results limit **(FREE SELF)** -The 100 results limit can be disabled if it breaks integrations developed using GitLab -12.4 and earlier. +The 100 results limit can break integrations developed using GitLab 12.4 and earlier. -To disable the limit while migrating to using the -[list a group's projects](#list-a-groups-projects) endpoint, ask a GitLab administrator -with Rails console access to run the following command: +For GitLab 12.5 to GitLab 13.12, the limit can be disabled while migrating to using the +[list a group's projects](#list-a-groups-projects) endpoint. + +Ask a GitLab administrator with Rails console access to run the following command: ```ruby Feature.disable(:limit_projects_in_groups_api) ``` +For GitLab 14.0 and later, the [limit cannot be disabled](https://gitlab.com/gitlab-org/gitlab/-/issues/257829). + ### Options for `shared_runners_setting` The `shared_runners_setting` attribute determines whether shared runners are enabled for a group's subgroups and projects. diff --git a/doc/api/oauth2.md b/doc/api/oauth2.md index dfb91283b50..61eaf0f36d7 100644 --- a/doc/api/oauth2.md +++ b/doc/api/oauth2.md @@ -194,8 +194,10 @@ NOTE: For a detailed flow diagram, see the [RFC specification](https://tools.ietf.org/html/rfc6749#section-4.2). WARNING: -The Implicit grant flow is inherently insecure. The IETF plans to remove it in -[OAuth 2.1](https://oauth.net/2.1/). +Implicit grant flow is inherently insecure and the IETF has removed it in [OAuth 2.1](https://oauth.net/2.1/). +For this reason, [support for it is deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/288516). +In GitLab 14.0, new applications can't be created using it. In GitLab 14.4, support for it is +scheduled to be removed for existing applications. We recommend that you use [Authorization code with PKCE](#authorization-code-with-proof-key-for-code-exchange-pkce) instead. If you choose to use Implicit flow, be sure to verify the `application id` (or `client_id`) associated with the access token before granting |