security - Manipulating a disabled attribute in client side; does JSF test properly if component is disabled? -


primefaces 3.5.10, mojarra 2.1.21, omnifaces 1.5

i thinking security issues.

i set component attribute component.getattributes() method. method returns hashmap attributes. safe set ("disabled", true)-pair in map disable component (for example p:inputtext-component)? use actionlistener, (phase 5 or 4) of jsf pipeline. possibly has implications render phase only. manipulate disabled attribute input method on client , post manipulated values. server make test if component disabled , rejects changes ?

what best way go ?

all components in panelgrid disabled:

xhtml: <p:panelgrid>   <my:component/>   <p:input value=#{mybean.value} /> </p:panelgrid>  bean:  (uicomponent component : l) {   component.getattributes().put("disabled", true);    recursion(....); } 

but manipulate disabled attribute input method on client , post manipulated values.

yes, enduser could.


does server make test if component disabled , rejects changes ?

yes, jsf based on component tree state, not on submitted value. part safe. way readonly , rendered attribtues.

see also:


Comments

Popular posts from this blog

assembly - 8086 TASM: Illegal Indexing Mode -

Java, LWJGL, OpenGL 1.1, decoding BufferedImage to Bytebuffer and binding to OpenGL across classes -

javascript - addthis share facebook and google+ url -