Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[GitLab CE] Redirect URI issue #39

Closed
Blasterdick opened this issue Jul 20, 2017 · 1 comment
Closed

[GitLab CE] Redirect URI issue #39

Blasterdick opened this issue Jul 20, 2017 · 1 comment

Comments

@Blasterdick
Copy link

Blasterdick commented Jul 20, 2017

I have a few questions about using integram.

  1. What Redirect URI should I use for Gitlab CE, if I'm running integram in the same kubernetes cluster, as the Giltab CE, and integram is accessible to GitLab via FQDN like integram.default.svc.cluster.local on port 80.

  2. What Scopes should I set for Redirect URI? (Gitlab 9.3.5)

Could you please help me to get this working? Thanks in advance.

@Blasterdick Blasterdick changed the title [GitLab CE] Redirect URI ussie & "too many colons in address" error [GitLab CE] Redirect URI issue & "too many colons in address" error Jul 20, 2017
@Blasterdick Blasterdick changed the title [GitLab CE] Redirect URI issue & "too many colons in address" error [GitLab CE] Redirect URI issue Jul 20, 2017
@Blasterdick
Copy link
Author

Blasterdick commented Jul 21, 2017

UPD:

  1. The Redirect URL should be like this: http(s)//sub.domain.com:port/auth/gitlab
  2. INTEGRAM_BASE_URL should be a complete FQDN (not an IP), ACCESSIBLE THROUGH THE INTERNET, so Telegram could open the links to it. Like http(s)//sub.domain.com:port
  3. It doesn't really matter what scopes do you use in Application settings on GitLab (they're added to a GET request by Integram anyways).
  4. INTEGRAM_PORT have to be pointed as well.

After that, everything works like a charm. Thanks, @requilence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant