Today we will take a look at how the external authentication mode works. Enabling this setting will force the user to go to the external authentication login landing page instead of the Sitecore Content Hub login page. Below are the steps to change the settings.
Navigate to the Manage page.
Navigate to Settings.
Search for PortalConfiguration.
Click Authentication under the PortalConfiguration.
5. Find authentication_mode under the Authentication. Set the value to Active, as shown below.
Today we are going to check two important properties of Sitecore Content Hub which could help you to resolve the issue of getting logged out.
Basically, both properties are part of Authentication within Content Hub Portal Configurations.
This property is as same as session Timeout, but the catch is this works irrespective of activity as this works on authentication cookie.
You can increase the session timeout by setting “ExpireTimeSpan” to any value in minutes up to the upper limit of 1440 minutes, the default value is 30 minutes.
Set this property to true, then it works whenever a request is done before ExpireTimeSpan which updates the expiration time for the authentication cookie, the default value is false.
Both of these settings should be configured under Manage->Settings->PortalConfiguration->Authentication.
The default value of the setting “SlidingExpiration” is false,
It’s been almost a year since I shared something, sorry for that as I was busy with personal things happening.
But now I have decided to share the knowledge back to the community with an innovative mini blog series for Sitecore Content Hub.
The series will have topics like Authentication, Related Assets, Asset Orientation, Notifications flow with Email, Archival flow, etc.
In this blog, we will deep dive into Related Assets from the End user’s point of view where most Content Editors and Administrators want to see the Assets which are Related to each other by some parameters. In our case, we took Location as a parameter and performed this activity.
Navigate to Manage > Schema > Asset, and create a taxonomy member to link M.Asset to R.Location (M.Asset is the Child of R.Location).
Create a new group something like “Related Assets Details”.
Add a new taxonomy member to this group and name it something like “RelativeLocation” While creating this on the Advanced tab, make sure Nested is set as true. Save and apply the changes to the Asset definition.
Navigate to Manage > Pages > Asset mass edit table page, and make sure that you add one more column to MassEditTable component to accommodate RelativeLocation member for Asset.
Now Navigate to Manage > Pages > Asset details page, and create a Search component change the setting to show it as a Panel with the title. Use the following filters inside the component:
System: Asset (M.Asset)
Fixed: Relation (Role: Parent) – RelativeLocation
In the Output Tab of the search, the component set the fields as below.
Once you create all of this go to the Assets page and select multiple Assets and Edit in Table where you could add the relative locations as below.
Go to the Asset details page of an asset. You should see all assets belonging to the same location displayed on the Asset details
You could create your own Taxonomy relations this is just an example.
The restriction is you can add only one filter to this at a time per search component.
To make it easier you can check the following video.
Now use “dotnet new epi-alloy-mvc –name Alloy12” command to create Alloy Demo templates.
You are now ready to install the database. Assuming you have done all the above steps correctly you now can use “dotnet-episerver create-cms-database ProjectName.csproj -S .\SQLEXPRESS -U sa -P “password” “ command to create the database for this current instance. (Note you need to use credentials and project names as per your local)
Now Use “dotnet build “ command to build the project.
Now use “dotnet run” command to run the project.
After this you can see in the terminal a localhost url with the port where this instance is running in my case, it is as below with url “https://localhost:5000/”
After creating the Admin user from the above panel you will be able to login into Optimizely.
Hope this article will help you with your local Optimizely 12 setup with the AlloyDemo project.