Another possibility could be SSO but still uses login token.  might be serving stale. Browser cache issue or webserver caching issue.  

Osgi web console have integration with basic http only. Addidtional with saml integration password is not stored in AEM repository.  You need to develop a plugin using websecurityprovider & not available out of the box.http://felix.apache.org/site/web-console-security-provider.html

From symptoms looks like there is internal implementation to guard against duplicate. Are you sure that for each record you need to pass same value?  If so can you please file daycare with actual requirements.  For now can you change value to be unique and then verify. Additionally you can debug you...

Dispatcher does not cache if there is no extension. For such requirement make use of rewrite rule.

If you are talking about  SiteMinder integrated with Sun OpenSSO support of saml2 thenYes you need to configure & details at [1].Destination at saml should take care of landing. No need of special implementation.Refer [1]Refer [1]Refer [1][1]http://docs.adobe.com/docs/en/cq/current/core/administerin...

No other configuration is required. When user is removed from ldap its membership will not be reflected in crx group immediately at that point. The group membership becomes eventually consistent once another user/same user logins after cache expiration.    Cq 5.3 had this issue & you should have hot...

you could find such example out of the box example profile update [1].  The key is you should provide form submit to same path. Btb you might have to plan well if it multiple publish instance how to sync with other instance.[1]   http://localhost:4502/cf#/content/geometrixx-outdoors/en/user/account....

Hi Bernard,    This has been tracked internally at CQ-22525,  GRANITE-6682.  With SP1 you can custom implement using miller column. Hoping it will fixed soon, In any case please file daycare for tracking.    Thanks,ShamTweet: @adobe_sham

Are you using crxde light?Technically it will work & fails only if there is node constraints.  What error are you getting?

Check on publish instance logs & thread dumps.  There will be some replication errors at the publish server why it is not responding or why it is busy.