summaryrefslogtreecommitdiff
path: root/vue.config.js
diff options
context:
space:
mode:
authorPaul Fertser <fercerpav@gmail.com>2024-07-03 17:11:03 +0300
committerPaul Fertser <fercerpav@gmail.com>2024-08-27 16:54:59 +0300
commit09a3b9e0b51c8c0a4ffff29581834c5f3b69b79e (patch)
tree70d327534290aa1347deb32657a9e1128c9ce925 /vue.config.js
parentb2acbcaa9cf7b1aa053216ca93ad2ad1f9846544 (diff)
downloadwebui-vue-09a3b9e0b51c8c0a4ffff29581834c5f3b69b79e.tar.xz
Use auth token when not communicating with bmcweb
Redfish backends other than OpenBMC bmcweb expect clients to authenticate using X-Auth-Token HTTP header as that's the only standard authentication method for Redfish sessions. This code falls back to using the token in case Session creation didn't result in obtaining an XSRF cookie (as should normally happen with bmcweb). Limitations: all WebSocket-based functionality can not work (JS-based NBD Virtual Media, IP KVM, SOL), page reload drops the session and requires to log in again. Tested: logging in, observing Overview and successfully logging out of an AMI MegaRAC BMC. Logging in and navigating around a bmcweb-running system which doesn't have the code to provide cookies for Session POST request (everything works as usual sans WS-based features). Change-Id: I81dc881193440d8d252dcd283b99915bd08c0c5e Signed-off-by: Paul Fertser <fercerpav@gmail.com>
Diffstat (limited to 'vue.config.js')
0 files changed, 0 insertions, 0 deletions