# Nexus IQ <-> Gitlab-Token problems

## post by m588 on Feb 6, 2023

Hello,

at first i want to say thanks for the last Bugfix in your 153 Release. Now it is possible for us to connect Nexus IQ and Gitlab.

I try to set up the configuration and created a token with API and WRITE_REPOISTORY rights in Gitlab:

Unfortainly, it seems not to work :

Over API:

```json
{
    "configurationComplete": {
        "valid": true,
        "message": null
    },
    "repoPrivate": {
        "valid": true,
        "message": null
    },
    "tokenPermissions": {
        "valid": false,
        "message": "The access token requires two scopes: 'api' (confirmed) and 'write_repository' (it can be manually checked in GitLab at: 'User Settings' > 'Access Tokens')."
    },
    "sshConfiguration": {
        "valid": true,
        "message": null
    }
}
```

I run a gitlab pipeline in a merge request but it doesn´t create a comment. I think its because he think the token is not right.

Do you have any hints what i am doing wrong?

Greets Marcus

## post by mfrost on Feb 6, 2023

Hi [@m588](https://community.sonatype.com/u/m588)! This doc may be a good place to start: [GitLab Configuration](https://help.sonatype.com/iqserver/integrations/nexus-iq-for-scm/source-control-configuration-overview/gitlab-configuration)

## post by m588 on Feb 7, 2023

Hi Maura,

i already followed the instructions contained in your link.

As you can see in my picture, i have created a Token with the needed permissions, but IQ say me the Token doesn´t have the right permissions.

Greets, Marcus

## post by mfrost on Feb 7, 2023

I would suggest opening a support ticket and someone can take a closer look! - an authorized support contact can [reach out to Sonatype Support here](https://support.sonatype.com/hc/en-us/requests/new) to open a support ticket.

## post by liermann.adrian on Jun 23, 2023

HI [@m588](https://community.sonatype.com/u/m588), did you find a Solution? I got the same Problem with Version 156.

Greetins,

Adrian

## post by rantoniuk on Jun 23, 2023

There is a (confirmed) bug opened by me internally about this, was not fixed yet.