Forum Discussion

z004f49p's avatar
z004f49p
New Member
6 months ago

gitlab personal token check failed

Hello all,

My company would like to introduce SmartBear collaborator additionally to Gitlab Merge requests, as SmartBear supports the Matlab simulink graphical presentation feature. Unfortunately there is no possibility to integrate the SmartBear with our own Gitlab instance, because the personal gitlab token of our own gitlab company instance doesn't pass the token length check from SmartBear collaborator. Our own gitlab instance generates prefixes on the beginning of each personal token, that's why the token length differs from the standard gitlab token length which is either 20 or 26 characters.

Currently our prefix is `CSC-`, but this will likely change to `CSC-glpat-` soon.

Is it possible to disable or bypass the personal token length check?

Thanks in advance!

2 Replies

Sort By
  • Humashankar's avatar
    Humashankar
    Champion Level 2
    6 months ago

    Hi z004f49p 

    Integrating SmartBear Collaborator with your company's GitLab instance due to personal token length differences.

    Sadly, disabling or bypassing the token length check is not a recommended or supported solution, as it may compromise security.

     

    As a substitute - I suggest you contact SmartBear support and provide them with details about your GitLab instance's custom token prefixes.

    They may be able to help you find a compatible solution or provide a configurable token length check in a future update.

     

    Warm Regards

  • EmilyMurray's avatar
    EmilyMurray
    Contributor
    6 months ago

    You cannot disable or bypass personal token length checking in SmartBear Collaborator. This check is an important part of system security and it is not recommended to change it. It is recommended that you contact SmartBear Collaborator support to find alternative solutions, they may be able to suggest other ways to integrate with your GitLab instance.