Details
-
Bug
-
Resolution: Fixed
-
Major
-
5.5.0, 5.5.1, 5.5.2, 6.0.0, 6.5.0
-
Untriaged
-
Unknown
Description
Currently, we always choose to perform token based auth for all the requests originating from the UI even if client certificate is configured in the browser and client certificate auth is enabled on the server. The expectation is that UI requests be authenticated based on client certificate when client certificate auth is enabled.
Attachments
Issue Links
- relates to
-
MB-32072 CLONE - Perform client cert auth for requests originating from UI
- Closed
For Gerrit Dashboard: MB-31558 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
100468,8 | MB-31558: New API to be used by UI to determine... | vulcan | ns_server | Status: MERGED | +2 | +1 |
100469,5 | MB-31558: UI changes to perform client cert auth. | vulcan | ns_server | Status: MERGED | +2 | +1 |
100490,4 | MB-31558: Add an API to get client cert auth state | vulcan | ns_server | Status: MERGED | +2 | +1 |
100491,9 | MB-31558: Enhance /uilogin to either perform... | vulcan | ns_server | Status: MERGED | +2 | +1 |
100547,1 | MB-31558: UI changes to perform client cert auth | master | ns_server | Status: ABANDONED | 0 | 0 |
101050,3 | MB-31558: Merge remote-tracking branch vulcan. | alice | ns_server | Status: MERGED | +2 | +1 |
101136,1 | Merge remote-tracking branch 'couchbase/alice'. | master | ns_server | Status: MERGED | +2 | +1 |