# Starting jobs while using Google Login plugin plus API Tokens

**URL:** https://community.jenkins.io/t/starting-jobs-while-using-google-login-plugin-plus-api-tokens/10473
**Category:** Using Jenkins
**Created:** [October 30, 2023, 7:09pm UTC](https://community.jenkins.io/t/starting-jobs-while-using-google-login-plugin-plus-api-tokens/10473 "2023-10-30T19:09:54Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![chernodog](https://avatars.discourse-cdn.com/v4/letter/c/4da419/32.png) [@chernodog](https://community.jenkins.io/u/chernodog)
#### Post date: [October 30, 2023, 7:09pm UTC](https://community.jenkins.io/t/starting-jobs-while-using-google-login-plugin-plus-api-tokens/10473/1 "2023-10-30T19:09:54Z")

</div>

I’m using the Google Login plugin with Jenkins (ie: Manage Jenkins → Security → Security Realm → Login with Google). I’m trying to switch my git hook to start jobs using API tokens instead of crumbs, [as described here](https://www.jenkins.io/doc/book/system-administration/authenticating-scripted-clients/).

However when running curl or wget as instructed

```auto
wget --auth-no-challenge \                                                                         
    --user="MY GOOGLE EMAIL" --password="MY API TOKEN I GENERATED AT /CONFIGURE" \
     https://myProject.jenkins.com/job/myJob/build

```

the request is redirected to google’s external identity provider. Is there a way to make this work? Do these two features not coexist?