ContributionsMost RecentMost LikesSolutionsRe: How to set predefined-only while creating GroupHub akashm you are right, it is a limitation we do not allow board level settings to be administered while creating a GroupHub. However, as a work around you could use what AndrewF has suggested or go to manage the internal individual board in admin portal --> Features --> Labels Settings and change it for now. We will try to internalise this suggestion. Re: Khoros Communities 21.5 Release Notes You are correct Claudius There should be no change or no user sso-id migration is needed if switching from existing SAML solutions (plugin based) to Core SAML. Just that customer is required to get it configured by our Support team and then set up the options (settings, idp metadata, and urls) again from the Admin portal. However, with the core offering of SAML available now, it is not mandatory to move to core SAML from plugin. Re: Cannot successfully archive message via API v2 jeffshurtliff The issue is in the request made. Body should be a json array, for example - [{ "messageId" : "174" }] and an optional "suggestedUrl" can be passed like - [{ "messageId" : "271", "suggestedUrl" : "https://test.com" }] Although it is a JSON array, it can only take one element for now, it was designed keeping the future bulk archive in the mind. For now only one thread id can be sent for archiving in one POST request. Re: API Access issue with / without SSO Hi korffr LiSESSIONID is a cookie session id and li-api-session-key is a session token, they both are different. instead of li-spi-session-key header, pass the LiSESSIONID as a cookie in the curl request with -b or --cookie option. It should work. for example: curl -X POST \ https://community.microfocus.com/api/2.0/messages \ -H 'content-type: application/json' \ -b "LiSESSIONID=<session_id_from_a_logged_in_cookies_section_of_your_browser>" \ -d '{ "data":{ "type":"message", "subject":"Test Subject", "body":"API Test body", "board":{ "id":"Management" } } }'