robertcavanna
Mentor
Joined 8 years ago
User Profile
User Widgets
Contributions
Re: Unable to get authorization code using V2 oauth2
I'm posting what worked for me here since I struggled with the first step for a while. The example included in the documentation for the request authorization looks like this: https://community.example_community.com/auth/oauth2/authorize?client_id=CbEwDo2NtAhXLSt4Y49D1yVE9D371eyZFWRSSXvNLvA=&response_type=code&redirect_uri=http%3A%2F%2Fredirect.example_community.com%2FgetaccessToken That example above implies that the client_id is un-encoded and the redirect_uri is URL encoded. It's the other way around. From my experience with this, I found that the client_id needs to be URL encoded and the redirect_uri must NOT be URL encoded, as in: https://community.example_community.com/auth/oauth2/authorize?client_id=CbEwDo2NtAhXLSt4Y49D1yVE9D371eyZFWRSSXvNLvA%3D&response_type=code&redirect_uri=http://redirect.example_community.com/getaccessToken Once I followed that format, using that URL in my browser while I was logged in, I was able to get a response with a code value in the URL. Note that the Code value that is returned in the URL is URL encoded. You'll need to decode it before using it in the next step when you request the access token and refresh token at: https://api.stage.lithium.com/auth/v1/accessToken?restapi.response_format=json Be sure to include the Content-Type and client_id in the header, and include the code, client_id, client_secret, redirect_uri, grant_type in the body in proper JSON format. I was using Advanced Rest Client to do this manually. This second step also needs to be done within a couple of minutes after getting the Code itself.Re: Oauth 2.0 : facing issue to get authorization code
I've been struggling with this error for a couple of weeks. I was finally able to get a code. The trick was making sure that the Client ID was URL encoded. The redirect_uri must NOT be encoded. Once I did that, the response has the code I was looking for in the URL. This conflicts with the developer documentation which shows an un-encoded client ID and an encoded return_uri. https://community.lithium.com/t5/Developer-Documentation/bd-p/dev-doc-portal?section=oauth2Label filter on the Search results page is not displayed
On the search results page in our community, we have the following filters, but no Labels filter: Here's the same filter on Lithium's community. Note the addition of the Labels filter: Looking at the Search Page Thread Filters page (a subset of the Message Search page), it has the following XML which appears to include a reference to the search.widget.label-filter. I believe this is what builds the search filters at the top of that page. <quilt layout="single-row-full" nestable="false" disableTopCssClass="false"> <add to="main-content"> <component id="search.widget.location-filter" isDropDown="true"/> <component id="search.widget.label-filter" isDropDown="true"/> <component id="search.widget.author-filter" isDropDown="true"/> <component id="search.widget.post-date-filter" isDropDown="true"/> <component id="search.widget.bling-filter" isDropDown="true"/> <component id="search.widget.type-filter" isDropDown="true"/> <component id="search.widget.content-filter" isDropDown="true"/> </add> </quilt> Are there other options I'm missing to get that Labels filter to show up in our community?
