Re: [I] seataNamingserver控制台密码不起作用 [incubator-seata]

Tue, 21 Oct 2025 22:31:49 -0700 


xingfudeshi commented on issue #7713:
URL: 
https://github.com/apache/incubator-seata/issues/7713#issuecomment-3430563656

   > > 
https://github.com/apache/incubator-seata/blob/2.5.0/console/src/main/java/org/apache/seata/console/security/CustomUserDetailsServiceImpl.java#L53
   > > <img alt="Image" width="2000" height="930" 
src="https://private-user-images.githubusercontent.com/19943636/503461249-86eb418a-4234-47cf-add6-3d43f6e8713d.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjEwMTUxOTksIm5iZiI6MTc2MTAxNDg5OSwicGF0aCI6Ii8xOTk0MzYzNi81MDM0NjEyNDktODZlYjQxOGEtNDIzNC00N2NmLWFkZDYtM2Q0M2Y2ZTg3MTNkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTEwMjElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUxMDIxVDAyNDgxOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTliNjNlNTkxMmNjMmI5NDUyNjg5ZjcyODYxZTllN2NkMWE2NjY2MzU0M2QxYTk0YjgzZDUwYzkxMTE1ZjlkOTQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.MoPXEWVJ5qDsL8rqaLOeiz6GVVWlr3ihvuewDzEJ4IY";>
 <img alt="Image" width="638" height="172" 
src="https://private-user-images.githubusercontent.com/19943636/503461298-65beb93f-d23e-4ba3-8b01-5ece2f3fc541.png?jwt=e
 
yJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjEwMTUxOTksIm5iZiI6MTc2MTAxNDg5OSwicGF0aCI6Ii8xOTk0MzYzNi81MDM0NjEyOTgtNjViZWI5M2YtZDIzZS00YmEzLThiMDEtNWVjZTJmM2ZjNTQxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTEwMjElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUxMDIxVDAyNDgxOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTAzNmQxNzlhNjc0NDFhZGFmNDJkOTlmYTdkMjc2ZGVkODJhZDFhZjljNWExYjk2NzY3ZjhhNmQzNjE3MzUzMzMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.6_EmVLmC_cnjrF6teISSGHJLwrH0-kDSeHvP4f8MMQc">
   > > Are you sure your configuration file was successfully mounted into the 
container? In my tests, a new password is only generated when 
`console.user.password` is not set. Also, changing the password in the 
application.yml file under conf takes effect.
   > 
   > <img alt="Image" width="840" height="477" 
src="https://private-user-images.githubusercontent.com/169338193/503465068-616288d4-4a6b-4ba2-b037-a44960df4a1d.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjExMTEyMzksIm5iZiI6MTc2MTExMDkzOSwicGF0aCI6Ii8xNjkzMzgxOTMvNTAzNDY1MDY4LTYxNjI4OGQ0LTRhNmItNGJhMi1iMDM3LWE0NDk2MGRmNGExZC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUxMDIyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MTAyMlQwNTI4NTlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT00MDZlYWRhZDA4MmNkYWU4ZTBhN2FlOTA1MDJhYzMxNmZmYjQ1NDc2OTliNjFjOGI2MzVhYWJiNDJkNmMzMTVhJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.eFCFZc14kI0Xe_6yHcW-RIvo9dDc-5WAuqaMNzyiR5M";>官方的文档有点小问题，路径有问题，配置文件应该是这个才对
 /seata-naming-server/resources/application.yml，容器里面的配置文件是
 这个，而不是/seata-namingserver/conf/application.yml
   
   The official Docker image uses JIB for building, ​​so​​ YAML files ​​reside 
in​​ the resources folder. ​​When​​ building ​​with a​​ Dockerfile ​​instead​​, 
these files ​​are placed in​​ the conf folder. The Dockerfile for Namingserver 
can be found here 
https://github.com/apache/incubator-seata/blob/2.x/distribution/docker/namingserver/Dockerfile


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to