Sergei Varaksin
Sergei Varaksin
**Describe the bug** Didn't find an appropriate repository for this issue. When you are using RESOURCE_PATH to land RP under a specific base path it works properly except notifications. Notificatiosn...
**Describe the bug** Azure SAML callbackURI doesn't support custom TLD like "private" etc **Expected behavior** allow any domain names **Screenshots** Attached **Versions:** - OS, Browser: Windows Server, Google Chrome Version...
Hi team, I have installed a new version of reportportal kubernetes (reportportal-24.1.0) in order to test it before we migrate from previous one. And SAML SSO looks like doesn't work...
### Describe the bug `az network application-gateway ssl-cert create --gateway-name *** --name test-cert --resource-group *** --key-vault-secret-id "https://***.vault.azure.net/certificates/certificate-name"` returns the following error: ``` Message: SecretId 'https://***.vault.azure.net/certificates/certificate-nam' specified in '/subscriptions/***/resourceGroups/***/providers/Microsoft.Network/applicationGateways/***/sslCertificates/test-cert' is invalid....
### Describe the bug ``` az appconfig feature set -n "appcg-main" --yes --label "test" --key ".appconfig.featureflag/test:test"; ERROR: The feature name derived from the specified key is invalid. Feature name cannot...
Screenshot attached. It is expected that you can use any domain name, especially for a private environment Could you please advice something or make a fix?