Nariman Abdullin

See example #2500

need to support markdown there

Dependencies between modules: |Module|Dependencies| |---|:---| |api-gateway| save-cloud-common, authentication-service | |authentication-service| save-cloud-common | |save-agent| save-cloud-common | |save-api| save-cloud-common | |save-api-cli| save-cloud-common, save-api | |save-backend| save-cloud-common, authentication-service, test-analysis-core, save-cosv, test-utils (only test),...

Actually we have the following hover:  So we set some status message, but it's not visible. raised: https://github.com/saveourtool/save-cloud/issues/2800

_For history_ # A&A in save-cloud: ## Basic auth: 1. Request comes to **api-gateway** with header `Authorization: Basic ***:***` 2. **api-gateway** has `UserDetailsRepositoryReactiveAuthenticationManager` (com.saveourtool.save.gateway.security.WebSecurityConfig) which uses internal endpoint in **backend**...

> > _For history_ > > # A&A in save-cloud: > > ## Basic auth: > > > > 1. Request comes to **api-gateway** with header `Authorization: Basic ***:***` >...

# TODO: - [ ] test API after changing - [ ] refactor `BackendService` and receive save's entity\class instead of spring's one to allow to provide ID - [ ]...

Also, a new avatar is not re-rendering on registration page (cc: @Cheshiriks )

> @akuleshov7 as far as I understand, this one will never be done, as we are not planning to store passwords. If I am wrong, please reopen an issue it's...

Will go by another workflow: 1. New contributor adds a comment to vulnerability 2. Owner adds this contributor to vulnerability (not implemented yet) 3. New contributor edits the vulnerability