MattV
Khoros Staff
Joined 17 years ago
User Profile
User Widgets
Contributions
Re: QraphQL Missing constraint on the messages collection
In classic/LiQL the post time constraint ended up being very inefficient, and even inaccurate with larger date ranges. So, assuming this omission is intentional in GraphQL, I'd say it was likely omitted because of similar reasons. I don't know the actual reason though; I'd have to confer with our internal dev teams to confirm the actual reason for post time not being a constraint.15Views0likes0CommentsRe: Can someone walk me through authenticating and using Postman with Aurora?
Here is my pre-request script for Postman for using the access token auth flow. var CryptoJS = require('crypto-js'); const clientID = pm.collectionVariables.get('clientID'); const clientSecret = pm.collectionVariables.get('clientSecret'); const secretSKey = pm.collectionVariables.get('secretSharedKey'); const encryptString = (str, salt) => { const sha256 = CryptoJS.algo.SHA256.create(); sha256.update(str); sha256.update(salt); return sha256.finalize().toString(); }; function getNonce(){ const characters = 'ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789'; let result = ''; for (let i = 0; i < 16; i++) { const randomIndex = Math.floor(Math.random() * characters.length); result += characters[randomIndex]; } return result; } var nonce = getNonce(); var epochTimeMinute = Math.floor(Date.now() / 60000); var key = clientID+':'+clientSecret+':'+nonce+':'+epochTimeMinute; var secret = encryptString(key,secretSKey); pm.collectionVariables.set("nonce",nonce) pm.collectionVariables.set("hash", secret); You can see, the nonce is just a random string of 16 alphanumeric characters, and that gets put in a part of th key, which we encrypt with SHA256. You then pass these parameters to that accessToken api in the request body { "client_id":"{{clientID}}", "client_secret": "{{clientSecret}}", "redirect_uri": "{{redirectURI}}", "grant_type": "client_credentials", "cc_hash": "{{hash}}", "hash_algorithm": "SHA256" } And the nonce gets passed as a header; nonce: {{nonce}}1View0likes0CommentsRe: Can someone walk me through authenticating and using Postman with Aurora?
GlennD wrote: I'm trying to move our data team over to the v3 bulk data API as the v2 version stopped working for them after we upgraded to Aurora. We use the Khoros SSO on our production community, will #1 Session Key (local account username and password) work for us? I've created a user but can't test signing in without getting directed to the SSO path What is the API path you are using? Unless you have a very strict or non-standard SSO configuration, I would expect the authentication API to work.43Views2likes2CommentsRe: Can someone walk me through authenticating and using Postman with Aurora?
I'm looking for the same walkthrough using Option #3 Access Token using pre-shared key (Dev Tools API apps). Can anyone help? For this, all you have to do is pass the the API token as a bearer key in the header. For example: Authorization: Bearer sDkKeY==39Views1like0CommentsRe: Problems with custom components in Aurora
In GitHub, check the Actions tab on your <phase>-main branch, and see if there are any errors. Other things to try: Check package.json and ensure the SDK version matches your community version (likely 24.12 or 25.1) Run npm i in your repo Run npm run build in your repo. This will do the same thing the actions in GitHub does. This will uncover any errors that may prevent your component from deploying properly23Views0likes0CommentsRe: Classic - Event Board Page force List View
Alright, after some sleuthing, looks like it might be a user setting of sorts. occasion.current_view_for_user Maybe you can use freemarker to check and set that setting for the user in common.init. For anonymous users, it seems to also use a cookie lia.anon.occasion.current_view_for_user. The valid values for the setting are: list or calendar Hopefully that gets you going in the right direction.62Views2likes0CommentsRe: Classic - Event Board Page force List View
Hey Mark, What does the quilt XML look like? On our test community, the event board page is loading in list view by default already. For reference, the default OccasionBoardPage.quilt.xml XML looks like: <?xml version="1.0" encoding="UTF-8"?> <quilt extends="Common" layout="one-column"> <add to="common-header"> <component id="primary-post-button" wrapper="lia-page-header"/> </add> <add to="main-content"> <component id="viewToggle"/> <component id="occasionsListView"/> </add> </quilt>27Views2likes1CommentRe: liqlAdmin in khoros aurora graphql API
Right now looks like this is only available in endpoints. I don't remember exactly, but I think it has a bit to do with security. Running GraphQL calls as admin, like with restadmin in classic, is very dangerous and has the potential to expose sensitive data, or allow users to modify data they shouldn't. So I think for technical reasons, at least for now, it is only available in endpoints.108Views3likes0CommentsRe: Handlebars Context Objects
I've tested this and found the same thing, even for fresh (server-side) page loads. This seems like a bug, so I've opened and internal bug ticket for this. If you want updates, file a support ticket, and could note this thread and/or this internal ticket ID: LIA-9607124Views1like0Comments