Callback URL of OAuth2 application created via client extension resets after server restart
Written By
Orsolya Hegedus
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
- After restarting the server, the callback URL for OAuth2 applications created via client extensions, gets reset to the default
@protocol@://localhost@port-with-colon@/o/oauth2/redirect, instead of the configured URL.
Resolution
- Client extensions always re-synchronize their configurations upon redeployment and DXP restart (except for batch client extensions). The client extension's configuration overrides any modifications made through the UI for OAuth2 Application settings. Therefore, the callback URI change in the UI is overwritten on the next server restart or new deployment.
Did this article resolve your issue ?