ContributionsMost RecentMost LikesSolutionsRe: Getting a 414 error code when updating messages via API Ignore me, I'm just being an **bleep** today apparently. For anyone else struggling through this vague and irrelevant error message, make sure you check to make sure you don't have tags turned OFF in the TKB where you're trying to update messages. Had a hunch to check some other settings and of course, tagging is turned off in the TKB that was giving me issues. Getting a 414 error code when updating messages via API We have a third party tool where we can update messages in TKBs. I'm using the session key for authentication using a non-SSO user with their username and password to get and refresh the session key. The user has Admin permissions across the entire community (for testing this), their email is verified, I've checked to make sure their account is correctly set up and working and that their permissions are correct. However, when I run the call for certain TKBs, I get this error: {"status":"error","message":"Permission Denied","data":{"type":"error_data","code":414,"developer_message":"","more_info":""},"metadata":{}} But when I run it for other TKBs, I don't get the error. I've looked at both TKBs and I'm scratching my head. Permissions are the same, settings are the same, essentially everything is the same besides which category they're in, but I've checked permissions in all categories/sub-categories and there are no differences. Any idea why this would happen or why I'm getting Permission Denied for a user with Admin permissions in some TKBs but not others? Re: Error with Oauth 2.0 Client Credentials workflow I am using that method for the epoch time and I am passing sha512 in the body when making the call. Maybe I have something incorrect in my headers or body? const res = await fetch(tokenUrl, { method: "POST", headers: { "Content-Type": "application/json", nonce: nonce, }, body: JSON.stringify({ client_id: clientId, client_secret: clientSecret, redirect_uri: redirectUri, grant_type: "client_credentials", cc_hash: ccHash, hash_algorithm: "sha512", }), }); And just for reference, here are some example values of what my epoch time, nonce, and cc hash are generating as (these are old values from earlier this week so I should be fine posting them here). I have also double checked that my client id, client secret, and shared secret key are all correctly passed as well. epoch time in minutes: 28888867 nonce: 6b6ba9ada7073749127d628bbdb5c7e4 cc hash (using sha512): 7898dac2f7fb09297bda0f13235ee29596a091ff4a63193a023e3336435f5f5c28a3f5bfe6992ed29383b1cc2fe032876c56f84fb3c99b281595873438dd0a1b Error with Oauth 2.0 Client Credentials workflow I'm trying to authenticate an api call in a typescript app using the oauth 2.0 client credentials workflow and I'm running into issues, I believe, with generating the CC Hash for this. This is for Community Classic. I have verified that I have the correct client id, client secret and shared secret key and that they're being pulled in correctly in my code. Not sure what I'm missing, but this is the error I see when I try to authenticate: {"error":"Authorization or API call failed","details":"Failed to obtain access token. Status: 403. Response: {\"status\":\"error\",\"message\":\"cc_hash is invalid.\",\"data\":{\"type\":\"error_data\",\"code\":214,\"developer_message\":\"The decryption failed. ccHash is Invalid\",\"more_info\":\"\"},\"metadata\":{}}"} Here's the relevant part of my Typescript code that's generating the CC Hash. Not sure if something is formatted incorrectly or what's not being generated correctly or causing it to return an invalid cc hash function generateCCHash(clientId: string, clientSecret: string, sharedSecretKey: string): string { try { const epochTimeMinute = getEpochTimeMinute(); const nonce = generateNonce(); const strToHash = `${clientId}:${clientSecret}:${nonce}:${epochTimeMinute}`; console.log("String to hash:", strToHash); const hash = crypto.createHash('sha512'); hash.update(strToHash, 'utf8'); hash.update(sharedSecretKey, 'utf8'); const hashResult = hash.digest('hex'); console.log("Generated hash (cc_hash):", hashResult); return hashResult; } catch (error) { console.error("Error generating CC-Hash:", error); throw error; } } Re: Error message when adding a query to handlebars component (Aurora) Just updated my SDK to v 24.8.1 and still getting the same issues unfortunately Re: Error message when adding a query to handlebars component (Aurora) I double checked and ran the SDK install again and it's showing I'm on Node 18.20.4 and SDK v 24.4.4 Error message when adding a query to handlebars component (Aurora) I'm trying to follow the documentation on creating a custom handlebars component in Aurora and I'm running into a weird error that I can't figure out. I have added the component via a GraphQL mutation and it works fine with some basic HTML, but once I try to follow this doc: https://developer.khoros.com/khorosauroradevdocs/docs/adding-graphql-queries-and-fragments-to-a-custom-handlebars-component I'm running into some issues: There's no docs (at least not that I've found) that explain how to get the bearer token or where the file should be stored or how that works when using GraphQL to upload a GraphQL file to use in a component (see here: https://developer.khoros.com/khorosauroradevdocs/docs/adding-graphql-queries-and-fragments-to-a-custom-handlebars-component#uploading-a-graphql-file-for-a-component-via-graphql) and I've been unable to figure out how to do this on my own. I've tried a few things with no success. If I try to follow the steps to add it manually, then I run into some strange errors. I'm running the SDK via VS code terminal which is working fine, but as soon as I follow the steps to add a "queries" folder and .graphql file to that folder within my component folder (e.g., components/myComponent/queries/myComponent.query.graphql) then I get an error in the VS Code terminal that says ""message": "The Content-Type header included with the request is not allowed (it should be either application/json or application/xml)."," and in my browser console when I try to load my custom component is: "Unable to fetch component to render for component id custom.widget.releaseTkbSidebar: Exception while fetching data (/component/render) : com.github.jknack.handlebars.HandlebarsException: releaseTkbSidebar:1:18: lithium.coreapi.components.ComponentTemplateApplyException: unable to apply template: releaseTkbSidebar: no query found matching the name 'releaseTkbSidebarQuery'. releaseTkbSidebar:1:18" Anyone know what's going on here? I've follow the dev docs and examples exactly (or as close as I can given that they've proven to be very inaccurate) and I'm out of things to test through trial and error. Here's what I have in my .hbs file for my custom component: <h2>Test!</h2> {{#gql "releaseTkbSidebarQuery"}} {{#with data.messages.edges as |edges|}} {{#each edges}} {{#with node as |message|}} <p>{{message.subject}}</p> {{/with}} {{/each}} {{/with}} {{/gql}} And here's what my .graphql query file looks like query releaseTkbSidebarQuery { messages { edges { node { id customFields subject } } } } My file structure looks like this Any help would be very much appreciated! Does anyone know how to change the display title of Custom Fields in Aurora? So I've figured out custom fields in Aurora using the new GraphQL API and I have a few test options in our stage instance, but I'm wondering if there's a way to change what displays in the UI. I've read through the dev docs on text key overrides and all the docs on custom fields and I haven't found anything about the display title for these in the UI. I'm guessing it has to do with either a form override or a text key override, but the docs on both are pretty sparse. Wondering if anyone else has figured this out yet. Thanks! Here's an example of what I'm talking about. We have a custom field on the user entity called "My School" and "myTest" and in the UI it shows "Value of [custom field name]". That's what we'd like to change, if at all possible. SolvedRe: Can someone walk me through authenticating and using Postman with Aurora? Perfect! I had another unrelated issue in Postman that was also causing me some issues, but I finally got it working this morning! Thanks so much. Whoever updates your developer docs may want to include this info in those docs for Aurora. Thanks again, MattV ! Re: Can someone walk me through authenticating and using Postman with Aurora? Thanks MattV but there seems to be one issue with the authentication that I can't quite sort out. On line 28 for 'Authorization' it's using the htaccess variable but you never specified what that should be in the environment variables.