I have SAML set  up to create new users with a default access group on creation. When new users log in to the site, their user account is created but they hit a 404 error on page load. We have a CUG enabled on the top level site page for the default user group that the user is added to on first log ...

Thanks! That first link might be useful. I hadn't come across that one yet.

So I have one attribute that comes in as a list, and when I set addGroupMemberships to true and set that attribute name as groupMembershipAttribute, none of the groups in the list are added.

The way our groups are coming in is multiples in an array or string in two different attributes, some of which need to be assigned and some of which don't. We were working with an Adobe consultant on how to process those attributes as user groups, and these are the solutions we were provided.  So I ...

I have SAML set up and working correctly. I am receiving and storing attributes from SAML into user profile nodes. I am currently using an AuthenticationInfoPostProcessor to turn the profile nodes into user groups however this process runs asynchronously to the AuthenticationHandler methods so new u...

Oh, that's awesome. Thank you SO much. I removed the workflows using the ACS Commons Workflow Remover tool, and now the timeline is working again.

When I go to the DAM to look at the revision history of any asset, I'm getting an error. The page spins for a while and then throws a 500 error on status.html and events.provider.html.The following are showing in my error log (truncated due to message size). I have no idea what's causing this or how...

By default, the cqPageLucene oak:index only indexes 4 nodes deep (*/*/*/*).  To increase the node depth for search, you can add additional includes under oak:index/cqPageLucene/aggregates/cq:PageContent with additional levels. By adding include4 (*/*/*/*/*) and include 5 (*/*/*/*/*/*) to my aggregat...

Unfortunately, I'm still getting the 403 error on the partial modal despite being able to access the URL directly.

In using the core Search component, I have discovered that content nested in 2 levels of Layout Containers is not showing in my search results while content in only one Layout Container does show.Is there a default setting that can be modified to pull back search results from within two nested Layou...