You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all,
Of course did pre-requisite archive and google searches, and do feel like a complete answer is still missing.
I'm trying to setup Netbox with Google Oauth2.0 , the other most relevant and recent post ( #9078 ) had a configuration example, but it was unclear if the poster was suggesting you fudge the secret/key with xxxx, or maybe it was simply implied you needed to get those values yourself.
It didn't seem overly tedious to just get a secret/key pair from the Google Cloud API, I went down that road and as soon as I had a key, my oauth started working immediately. Whee... but there is a catch... more on that in a second.
Also, this site was interesting ( https://questionable.one/post/secure-netbox-with-oauth2/ ) , but I found it after my Google Oauth was already working. So, I'm intrigued and confused about all the work that is shown setting up Nginx, vouch-proxy, okta, etc. It seems far more complicated than what worked for me, right out of the figurative box?
However, Google really views everything you do as you were an original "developer" and that you are making a whole new application from scratch. To that end, before you can use the API unrestricted you have to publish your application, and they have some requirements that seem a bit over the top, and they perform a multi-day manual verification:
And at that point, I started second guessing myself... Did I take a wrong turn? Shouldn't there be an 'easy way' to get a Google oauth2 secret/key pair for 'simple' authentication? More googling, and I couldn't find anything simpler, all roads led back to the developer API. I can and will fulfill Google's requests to get 'my app' published, but just hoping to make it easier for someone else, particularly if anyone else has setup Netbox with Google Oauth2.0 and would care to share their experience?
In summary, on the plus side, Netbox configuration while not as simple as the previous poster implied, does seem to be fairly simple and functions well. On the negative side, Google's requirements are slightly tedious, unless there is a simpler way anyone is aware of?
And I don't think it matters much... but I installed NetBox 3.2.7 on a Ubuntu 20.04.01 AWS instance, as noted, with Nginx. Very vanilla setup.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
Of course did pre-requisite archive and google searches, and do feel like a complete answer is still missing.
I'm trying to setup Netbox with Google Oauth2.0 , the other most relevant and recent post ( #9078 ) had a configuration example, but it was unclear if the poster was suggesting you fudge the secret/key with xxxx, or maybe it was simply implied you needed to get those values yourself.
It didn't seem overly tedious to just get a secret/key pair from the Google Cloud API, I went down that road and as soon as I had a key, my oauth started working immediately. Whee... but there is a catch... more on that in a second.
Also, this site was interesting ( https://questionable.one/post/secure-netbox-with-oauth2/ ) , but I found it after my Google Oauth was already working. So, I'm intrigued and confused about all the work that is shown setting up Nginx, vouch-proxy, okta, etc. It seems far more complicated than what worked for me, right out of the figurative box?
So, back to Google and my 'catch'... I walked through Google's documentation (and i've done it in the distant past, so it was semi-familiar): https://support.google.com/googleapi/answer/6158849?hl=en
However, Google really views everything you do as you were an original "developer" and that you are making a whole new application from scratch. To that end, before you can use the API unrestricted you have to publish your application, and they have some requirements that seem a bit over the top, and they perform a multi-day manual verification:
And at that point, I started second guessing myself... Did I take a wrong turn? Shouldn't there be an 'easy way' to get a Google oauth2 secret/key pair for 'simple' authentication? More googling, and I couldn't find anything simpler, all roads led back to the developer API. I can and will fulfill Google's requests to get 'my app' published, but just hoping to make it easier for someone else, particularly if anyone else has setup Netbox with Google Oauth2.0 and would care to share their experience?
In summary, on the plus side, Netbox configuration while not as simple as the previous poster implied, does seem to be fairly simple and functions well. On the negative side, Google's requirements are slightly tedious, unless there is a simpler way anyone is aware of?
And I don't think it matters much... but I installed NetBox 3.2.7 on a Ubuntu 20.04.01 AWS instance, as noted, with Nginx. Very vanilla setup.
Thanks in advance for any responses.
Beta Was this translation helpful? Give feedback.
All reactions