= Fixed detection of Bitbucket Server access tokens in workspaces Before this update, as a result of a bug, Bitbucket Server access tokens were not detected link: https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.7/html-single/user_guide/index#using-a-git-provider-access-token [as Kubernetes Secrets]. The editor in the workspace did not detect an access token for Bitbucket Server. With this update, individual users can resume using Bitbucket Server access tokens as Kubernetes Secrets. NOTE: {prod-short} supports administrator-enabled link: https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.7/html-single/administration_guide/index#configuring-oauth-1-for-a-bitbucket-server [OAuth 1.0] or link: https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.7/html-single/administration_guide/index#configuring-oauth-2-for-a-bitbucket-server [OAuth 2.0] for a Bitbucket Server. This is more user-friendly than individual users' Bitbucket Server access tokens.