If you have two domains that point to OpenAM, you may want to have a confirmation email URL that depends of the domain where you start the request:
If you send the email from "http://rock.example.com:8080/openam/XUI/#forgotPassword/", you want to have a confirmation URL with the same domain
but you also want to be able to use it from the other domain "http://openam.example.com:8080/openam/XUI/#forgotPassword/" and therefore, having a confirmation URL that look like http://openam.example.com:8080/openam/XUI/confirm.html?confirmationId=pT1XtJ3FiKw6Ylt+WCmbs4aC32M=&tokenId=kutn6LOiia6HarCH+OXjisZyUqw=&username=demo&realm=/
Today, if you define a relative path as a confirmation URL, OpenAM doesn't append the current deployment URL.
We can imagine that the setting "/XUI/confirm.html" could be valid and represent the relative path.