Question
Lantiqx Systems India Private Limited
IN
Last activity: 17 Dec 2024 0:04 EST
DX Custom Component
Hello team,
I have built a component called Slider in SDK. While i am running the story book in visual studio i am getting the output as per the requirement and i am able to add in App studio after publishing the component but when i am running it is not displaying in the portal.
Can you guys help me out with this issue?
Regards,
Mamatha Adiraju
***Edited by Moderator Marije to change type from General to Product, added Product details and Capability tags****
Pegasystems Inc.
CA
Are you able to see the new component in Rule-UI-Component?
Lantiqx Systems India Private Limited
IN
Yes, I am able to see, even I have added it in portal also, but the widget is not visible in the output.
Regards,
Mamatha Adiraju
Updated: 11 Dec 2024 9:53 EST
Pegasystems Inc.
CA
Thanks for confirming. Can you please create another field-level component (TextField) and publish it to isolate whether the issue is specific to the slider component or all components?
Please note: Slider is available in OOTB in 24.2 version for Integer Data type.
Rulesstack Private Limited
IN
Hi @Mamatha Adiraju,
- Pega Logs: Check the logs for any errors related to component rendering.
- Browser Network Logs: Inspect the browser's developer tools network tab to ensure that all necessary resources are being requested and successfully loaded. Missing resources could cause the component to fail.
Lantiqx Systems India Private Limited
IN
Hi @Mohd Qizer Uddin, I have even checked the logs I am getting the error like "Error while processing JWT JSON web token is rejected during signature verification due to bad signature : Expired JWT" Could you please suggest me the solution regarding this issue.
Updated: 11 Dec 2024 1:06 EST
Rulesstack Private Limited
IN
I think Expired JWT error, you need to either refresh the token or issue a new one.
or
Fixing the "Bad Signature" Issue
- Check the JWT Signature: If the signature is being rejected, the problem could be twofold:
- The JWT might have been tampered with.
- The signature verification key (or algorithm) might be incorrect.
- Ensure the correct signing key: Verify that the key used to sign the JWT is the same key being used for signature verification. This is particularly relevant if you’re using a public/private key pair or a shared secret.
Lantiqx Systems India Private Limited
IN
Updated: 11 Dec 2024 2:10 EST
Rulesstack Private Limited
IN
Refresh the JWT Token
-
OAuth 2.0 Refresh Token: If the JWT token is issued as part of an OAuth 2.0 flow, you likely have a refresh token that can be used to obtain a new JWT token without requiring the user to re-authenticate.
- Request a new access token using the refresh token: Use the refresh token to request a new access token from your authorization server. The request typically looks like this:
POST /token,
grant_type=refresh_token, refresh_token=YOUR_REFRESH_TOKEN , client_id=YOUR_CLIENT_ID , client_secret=YOUR_CLIENT_SECRET
Rulesstack Private Limited
IN
Hi @Mamatha Adiraju ,
If you find a solution, please close this thread by marking it as the accepted solution.