Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

private_token= vsjob_token=#3234

Unanswered
stdedos asked this question inQ&A
Discussion options

I am not talking about theaxl89@746c25f issues - but does the actualkwarg make a difference?

I have also seen

classPrivateTokenAuth(TokenAuth,AuthBase):
def__call__(self,r:PreparedRequest)->PreparedRequest:
r.headers["PRIVATE-TOKEN"]=self.token
r.headers.pop("JOB-TOKEN",None)
r.headers.pop("Authorization",None)
returnr
classJobTokenAuth(TokenAuth,AuthBase):
def__call__(self,r:PreparedRequest)->PreparedRequest:
r.headers["JOB-TOKEN"]=self.token
r.headers.pop("PRIVATE-TOKEN",None)
r.headers.pop("Authorization",None)
returnr
(main-as-of-now)

I mean - the "end result" is still

gitlab.exceptions.GitlabGetError: 404: 404 Project Not Found

Because probably

You can use a job token to authenticate with GitLab to access another group or project’s resources (the target project). By default, the job token’s group or project must beadded to the target project’s allowlist.

You must be logged in to vote

Replies: 0 comments

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
Q&A
Labels
None yet
1 participant
@stdedos
[8]ページ先頭
©2009-2025 Movatter.jp