Forum Discussion

VincentGabou's avatar
VincentGabou
Guide
11 years ago

Replicate Me Too component, or any ID-required non-contract component to a custom component

Hello,   I am currently trying to integrate a Q&A page that will be extensively customized. One of the "customization" I was trying to implement was to be able to have "Me Too" button on the Q&A ma...
clemlith's avatar
clemlith
Expert

Hi VincentGabou and AdamA ,

Thanks for sharing your thoughts about this features and its limitations in its current state.

 

If Vincent try to replicate the behavior of a me too button he has to handle all the logic related to the authentication/registration status.

And as per my understanding there's also the management and the creation of a token which is needed to perfom an action in the platform.

Indeed at the end of every URL holded by a kudo or me too button there is ticket parameter (e.g &ticket=aMivVgLAcKnS_11676)

 

AdamADo you know if this token / parameter is mandatory ? If yes is there a way to generate it through an api call ?

 

Best,

Clement

AdamA's avatar
AdamA
Khoros Oracle
11 years ago

VincentGabou Yes, the rest call you referenced is the one you would use to give a me too. I believe a value of -1 is what we consider "not helpful" and a value of 1 is considered to be helpful.

 

Add (or change) the Me Too on a Question:

 

/messages/id/<message-id>/ratings/key/question_metoo/ratings/add?rating.value=1

 

Revoke the Me Too on a Question:

 

/messages/id/<message-id>/ratings/key/question_metoo/ratings/revoke​

 

clemlith If this is used in the context of a custom component, as freemarker code, then the call will be made as the current user. If made via REST over HTTP then you would need to use one of our auth mechanisms to make the call as the current user. One of the mechanisms is to pass a sso.authentication_token along with the request (if you are using SSO). This token can be generated by using a REST call (see links below for more details). Please note that the sso.authentication_token is different that the token (aka ticket) used by the application that you saw in the out-of-the-box UI (ticket=aMivVgLAcKnS_11676). The token used by the out-of-the-box UI is not intended to be used for REST or for customizations. Also, the action links in the OOTB UI are not intended to be used when building customizations, the REST API should be used in those cases.

 

Auth for Non SSO: 

 

http://community.lithium.com/t5/Single-Sign-On-SSO/Authenticating-via-REST-API-non-SSO/ta-p/61862

 

Auth for SSO: 

 

https://community.lithium.com/t5/Community-API/bd-p/developers-rest-api?page=authentication#sso