Request parameter of a xhtml page

Unfortunately that doesn't work (for my setup).

Solution (seems more like a hack to me - therefore any corrections are welcome):

• Call ManagedBean in xhtml via p:remoteCommand or similar method
• Read parameter via FacesContext.getCurrentInstance().getExternalContext().getRequestParameterMap().get("myParam") and store it as a param in ManagedBean
• Read parameter from ManagedBean in ScriptBox

Yep sounds definitively like a hack. Maybe you can share why and how you trigger the redirect in first place and look for an alternative solution in this area.

We are trying to implement a OAuth flow. Usually this is implemented by using redirects in a browser. Also OAuth is adding parameters to the URI. So this means we need to read them from there. Further the OAuth system will check the redirect URI, that means we can't jump from URI_1 and then use redirect URI_2. The implementation currently is as follows ( https://jira.axonivy.com/confluence/display/~jmo/OAuth+flow+with+Ivy ) : - there is a "Display Accounts" process which displays a dialog (xhtml) - in the "xhtml" there are 2 calls which run asynchronously ...

... a) <f:viewaction> to calculate the URI and read request params if available b) <p:remotecommand> to load the data to be displayed, which also triggers the OAuth flow if necessary -> sub process getAccountData() - as you can see in the gfx, "Redirect to OAuth" redirects to the OAuth uri to start the OAuth flow - after the OAuth flow the "xhtml" is loaded again but the process starts right with getAccountData() ... i guess due to loading of "xhtml"

=> imho - in a "user dialog method start", one should be able to map the request params like in a "request start"