bdlee420 commented on issue #283:
URL: https://github.com/apache/pulsar-manager/issues/283#issuecomment-1472454775
A couple of things have changed since the last comments. pulsar/pulsar is no
longer a valid username password combo out of the box even if you disabled
user.management.enable. The documentation is wrong. For windows -> cmd users,
you can create a CMD file and run this command to create a new super user:
`for /F %%I in ('curl http://localhost:7750/pulsar-manager/csrf-token') do
set CSRF_TOKEN=%%I
curl -H "X-XSRF-TOKEN: %CSRF_TOKEN%" -H "Cookie: XSRF-TOKEN=%CSRF_TOKEN%;"
-H "Content-Type: application/json" -X PUT
http://localhost:7750/pulsar-manager/users/superuser -d "{\"name\": \"admin\",
\"password\": \"apachepulsar\", \"description\": \"test\", \"email\":
\"[email protected]\"}"`
Username = admin
Password = apachepulsar
Next. You don't HAVE to create the Pulsar Service and Pulsar Manager Client
at the same time in the same file like vip32 suggested. If you want to do it
separately you can, but it will create issues when adding a new environment
because you have to remove the pulsar linked service in the compose file. For
me the Service URL that worked was http://host.docker.internal:8086 (my service
runs on 8086, default is 8080).
These didn't work.
http://127.0.0.1:8086
http://localhost:8086
Maybe a host file change would have made them work, but I know
host.docker.internal works since I have that host file entry.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
