webUI ，Unable to reach auth service. [auth:true] #5522
Open
Nobody has claimed this yet.
stale
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
I did the following：
- Modify the vagrantFile file
config.vm.network "forwarded_port", guest: 80, host: 8081
config.vm.network "forwarded_port", guest: 443, host: 8443
- vi /opt/stackstorm/static/webui/config.js
'use strict';
angular.module('main')
.constant('st2Config', {
hosts: [{
name: 'default',
url: 'https://127.0.0.1:8443/api',
auth: 'https://127.0.0.1:8443/auth'
}]
// hosts: [{
// name: 'Dev Env',
// url: '//172.168.50.50:9101'
// }, {
// name: 'Express',
// url: '//172.168.90.50:9101',
// auth: true
// }]
});
Problem:
https://127.0.0.1:8443/#/history
Unable to reach auth service. [auth:true]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the Vagrantfile port mappings and /opt/stackstorm/static/webui/config.js, then reproduce the problem at https://127.0.0.1:8443/#/history. Trace the configured auth URL and identify why the web UI cannot reach it. Done means the history page no longer reports “Unable to reach auth service. [auth:true]” with this setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angularjs
- Domain
- authentication, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100