Open abhikum1 opened 5 years ago
@abhikum1 Thank you for your report. Can you confirm from looking at the requests in the developer tools that the call to /tokenStore?key=
returns the correct GitLab access token?
@MartinBenninger sounds like the same issue I've experienced recently while using it. For me, from looking at the screenshot, it looks like as if the access token key and value are missing.
@innerjoin yes the correct key is returned: {"token":"uoho3ewxhPgbTk4ycxCe"}
Also, while looking at the console i noticed the browser blocked Cross Domain Request.
However, i have allowed cross domain requests in the ccm application.
@abhikum1 Did you follow the the 3.3 White List Configuration instructions from the documentation?
@MartinBenninger @SBI- Not sure whether the Whitelist configuration is sufficient. If I remember correctly, it applies only when going through the proxy
endpoint, which not seems to be the case here. What needs to be configured in addition for cross origin requests here?
@abhikum1 Which version of gitlab are you using, and what kind of webserver / proxy-setup is being used? It looks like whatever reverse-proxy gitlab is behind is not handling any of the CORS headers.
Gitlab version : 11.10.8 we are using docker container hosted on RHEL https://docs.gitlab.com/omnibus/docker/ there is no proxy-setup being used as far as i know but i will confirm this with my team.
That doesn't preclude an error on our side, by the way. It's just something I noticed in the example screenshot. It's also possible it's just missing from the crop.
Hello Team,
I am trying to connect git with RTC using your extension. After registering the GitLab repo, while entering my access token the screen is prompting me to again enter it.
I have double cheked the setup of the dependencies and they seem to be working. Also, I have cross checked my access token and it seems to be correct. On opening the developer tools i see a request is failing (PFB) for screenshot.
Looking forward for you reply.
Reagards, Abhishek