Status Update
Comments
ta...@gmail.com <ta...@gmail.com> #2
Best Regards,
Josh Moyer
Google Cloud Platform Support
pa...@google.com <pa...@google.com> #3
jt...@gmail.com <jt...@gmail.com> #4
ka...@gmail.com <ka...@gmail.com> #5
fr...@gmail.com <fr...@gmail.com> #6
de...@derekperkins.com <de...@derekperkins.com> #7
[Deleted User] <[Deleted User]> #8
zi...@gmail.com <zi...@gmail.com> #9
qu...@gmail.com <qu...@gmail.com> #10
fr...@gmail.com <fr...@gmail.com> #11
sk...@gmail.com <sk...@gmail.com> #12
de...@derekperkins.com <de...@derekperkins.com> #13
jt...@gmail.com <jt...@gmail.com> #14
de...@derekperkins.com <de...@derekperkins.com> #15
[Deleted User] <[Deleted User]> #16
ti...@terran.io <ti...@terran.io> #17
al...@gmail.com <al...@gmail.com> #18
[Deleted User] <[Deleted User]> #19
[Deleted User] <[Deleted User]> #20
2018 =(
dr...@mypacificacademy.net <dr...@mypacificacademy.net> #21
al...@gmail.com <al...@gmail.com> #22
is...@google.com <is...@google.com>
wb...@gmail.com <wb...@gmail.com> #23
[Deleted User] <[Deleted User]> #24
[Deleted User] <[Deleted User]> #25
ka...@gmail.com <ka...@gmail.com> #26
de...@giantthinkwell.com <de...@giantthinkwell.com> #27
tr...@gmail.com <tr...@gmail.com> #28
na...@gmail.com <na...@gmail.com> #29
da...@illumon.com <da...@illumon.com> #30
sy...@gmail.com <sy...@gmail.com> #31
ho...@gmail.com <ho...@gmail.com> #32
[Deleted User] <[Deleted User]> #33
hi...@smiledu.com <hi...@smiledu.com> #34
de...@gmail.com <de...@gmail.com> #35
[Deleted User] <[Deleted User]> #36
Definitely useful feature at least provide a way to alias this.
+1
me...@gmail.com <me...@gmail.com> #37
ja...@terratrue.com <ja...@terratrue.com> #38
[Deleted User] <[Deleted User]> #39
sy...@gmail.com <sy...@gmail.com> #40
shouldn't be a very difficult implementation but benefits lots of people
[Deleted User] <[Deleted User]> #41
ec...@gmail.com <ec...@gmail.com> #42
ra...@gmail.com <ra...@gmail.com> #43
da...@google.com <da...@google.com> #44
da...@google.com <da...@google.com> #45
ro...@redfin.com <ro...@redfin.com> #46
+1 here too. But the problem is also with disks. We currently use part of hostname in the name. Sometimes a machine has to be renamed and it's not possible.
ad...@gmail.com <ad...@gmail.com> #47
ta...@gmail.com <ta...@gmail.com> #48
+1
hi...@gmail.com <hi...@gmail.com> #49
mi...@datanova.com.au <mi...@datanova.com.au> #50
Whe the ETA for this simple important request?
ro...@google.com <ro...@google.com>
ce...@google.com <ce...@google.com> #51
[Deleted User] <[Deleted User]> #52
fr...@google.com <fr...@google.com> #53
da...@zieglerlabs.com <da...@zieglerlabs.com> #54
Hello,
Thanks for reaching out to us!
The Feature Request has been created and the Product Engineering Team is working on this request. At this moment, there is no ETA to this request. Thank you for your trust and continued support to improve Google Cloud Platform products.
In case you want to report a new issue, please do not hesitate to create a new
ga...@gmail.com <ga...@gmail.com> #55
ji...@google.com <ji...@google.com> #56
Hello,
Thank you for pointing out the redirect URIs, this issue is meant to capture such important features in OAuth configurations. However there is still no ETA for this. Please make sure you hit +1 and star this issue as to provide visibility on the importance of this request on to the product team.
ma...@ada.com <ma...@ada.com> #57
[Deleted User] <[Deleted User]> #58
ra...@codeclouds.in <ra...@codeclouds.in> #59
lo...@gmail.com <lo...@gmail.com> #60
[Deleted User] <[Deleted User]> #61
da...@gmail.com <da...@gmail.com> #62
fr...@google.com <fr...@google.com> #63
Engineering team is still working on this. There is still no timeline or implementation guarantee for feature requests.Please make sure you hit +1 and star this issue as to provide visibility on the importance of this request on to the product team.
jr...@gmail.com <jr...@gmail.com> #64
You've grown so much over the past 7 years and I'm very proud of your persistence. The future is very bright for you. 😎
Enjoy your special day little guy! 🥳 🍻
[Deleted User] <[Deleted User]> #65
fc...@gmail.com <fc...@gmail.com> #66
[Deleted User] <[Deleted User]> #67
th...@gmail.com <th...@gmail.com> #68
+1
si...@gmail.com <si...@gmail.com> #69
"Authorized JavaScript origins" is heavily used in Firebase Login to authorize your custom authDomain in firebase config file.
And "Authorized redirect URIs" for facebook login redirect too.
Maybe this issue could at least be implemented through Firebase Auth?
Being able to authorize a sub-domain to work for a custom firebase authDomain on-the-fly would be so neat!
Native implementation of course would be even better!
PS: This feature is CRITICAL for login in a SaaS product team pls pls pls!
Keep up the work guys <3
jo...@front.com <jo...@front.com> #70
vi...@gmail.com <vi...@gmail.com> #71
Otherwise be able to add new URIs via the API, in order to add the client URIs before making the token request by the client in the subdomain...
+1
[Deleted User] <[Deleted User]> #72
am...@khare.co.in <am...@khare.co.in> #73
or...@gmail.com <or...@gmail.com> #74
[Deleted User] <[Deleted User]> #75
[Deleted User] <[Deleted User]> #76
ja...@gmail.com <ja...@gmail.com> #77
pa...@gmail.com <pa...@gmail.com> #78
gi...@gmail.com <gi...@gmail.com> #79
ch...@vortexa.com <ch...@vortexa.com> #80
d....@space307.com <d....@space307.com> #81
ar...@gmail.com <ar...@gmail.com> #82
le...@kyosk.app <le...@kyosk.app> #83
pa...@gmail.com <pa...@gmail.com> #84
de...@gmail.com <de...@gmail.com> #85
[Deleted User] <[Deleted User]> #86
ma...@gmail.com <ma...@gmail.com> #87
no...@guitup.com <no...@guitup.com> #88
jo...@smartrr.com <jo...@smartrr.com> #89
ap...@jellyfishtechnologies.com <ap...@jellyfishtechnologies.com> #90
print('+1');
}
ge...@gmail.com <ge...@gmail.com> #91
[Deleted User] <[Deleted User]> #92
tn...@hex.tech <tn...@hex.tech> #93
ja...@gmail.com <ja...@gmail.com> #94
+1 - what is the recommended workaround for this? E.g. should I use an iframe on subdomains, containing a mini auth page on the top-level domain?
ma...@sonicjobs.com <ma...@sonicjobs.com> #95
ma...@huntandhackett.com <ma...@huntandhackett.com> #96
I long for the beauty and love that I got familiar with using GCP.
I'm at a crossroads, doing something manually in our CI/CD - or leave GCP to betroth myself to Azure.
There is no choice left, as manual labor is slavery.
Azure it is.
am...@gmail.com <am...@gmail.com> #97
an...@gmail.com <an...@gmail.com> #98
ai...@gmail.com <ai...@gmail.com> #99
sa...@gmail.com <sa...@gmail.com> #100
su...@vectoscalar.com <su...@vectoscalar.com> #101
bo...@plana.solutions <bo...@plana.solutions> #102
hs...@nsquared.io <hs...@nsquared.io> #103
al...@flexrentalsolutions.com <al...@flexrentalsolutions.com> #104
[Deleted User] <[Deleted User]> #105
[Deleted User] <[Deleted User]> #106
ol...@gmail.com <ol...@gmail.com> #107
Makes using dynamic domains for each branch like in Vercel very difficult to use.
ye...@gmail.com <ye...@gmail.com> #108
ja...@unthread.io <ja...@unthread.io> #109
an...@ownerfactory.com <an...@ownerfactory.com> #110
va...@google.com <va...@google.com>
gh...@google.com <gh...@google.com>
on...@kontentino.com <on...@kontentino.com> #111
al...@eadem.com <al...@eadem.com> #112
hu...@gmail.com <hu...@gmail.com> #113
vh...@gmail.com <vh...@gmail.com> #114
la...@gmail.com <la...@gmail.com> #115
ch...@gmail.com <ch...@gmail.com> #116
[Deleted User] <[Deleted User]> #117
ne...@gmail.com <ne...@gmail.com> #118
li...@gmail.com <li...@gmail.com> #119
ma...@begrateful.org <ma...@begrateful.org> #120
[Deleted User] <[Deleted User]> #121
ra...@gmail.com <ra...@gmail.com> #122
ho...@eano.com <ho...@eano.com> #123
[Deleted User] <[Deleted User]> #124
ho...@gmail.com <ho...@gmail.com> #125
vp...@ext.uber.com <vp...@ext.uber.com> #126
sn...@ext.uber.com <sn...@ext.uber.com> #127
br...@gmail.com <br...@gmail.com> #128
ma...@magnetcustomer.com <ma...@magnetcustomer.com> #129
ad...@firstpromoter.com <ad...@firstpromoter.com> #130
de...@policyme.com <de...@policyme.com> #131
Please add this feature to gcloud api
sh...@qburst.com <sh...@qburst.com> #132
th...@ae.studio <th...@ae.studio> #133
ha...@gmail.com <ha...@gmail.com> #134
ka...@gmail.com <ka...@gmail.com> #135
si...@gmail.com <si...@gmail.com> #136
wa...@hotmail.fr <wa...@hotmail.fr> #137
[Deleted User] <[Deleted User]> #138
1v...@gmail.com <1v...@gmail.com> #139
dr...@gmail.com <dr...@gmail.com> #140
di...@gmail.com <di...@gmail.com> #141
di...@gmail.com <di...@gmail.com> #142
fi...@uppedevents.com <fi...@uppedevents.com> #143
mk...@qualtrics.com <mk...@qualtrics.com> #144
[Deleted User] <[Deleted User]> #145
pa...@gmail.com <pa...@gmail.com> #146
ad...@pulselive.tv <ad...@pulselive.tv> #147
br...@proofpilot.com <br...@proofpilot.com> #148
va...@google.com <va...@google.com>
rw...@foxhire.com <rw...@foxhire.com> #149
al...@gmail.com <al...@gmail.com> #150
va...@google.com <va...@google.com>
j....@pons.de <j....@pons.de> #151
This bug is as old as a Microsoft Lumia 950 mobile phone, or James Bond "Spectre".
ak...@gmail.com <ak...@gmail.com> #152
an...@du.co <an...@du.co> #153
> Status: New
Excuse me?
ad...@wisk.aero <ad...@wisk.aero> #154
This ticket has been around longer than I've been an engineer. Will it still be around after I retire?
pr...@gmail.com <pr...@gmail.com> #155
an...@intellum.com <an...@intellum.com> #156
+1
ma...@gratefulgiving.org <ma...@gratefulgiving.org> #157
unknown contacts.
Click here to create a vendor profile.
<
Or click here
<
if you know them personally, or if your email is not a solicitation.
This is an automated message.
Description
Since subdomain wildcards aren't allowed, there really should be an API to update domains. That way I can automatically add their subdomain as a verified javascript origin / redirect uri. Without that, I can't have self-service customers because they won't be able to login until we manually add it.
This now seems to be the preferred way to provide customer access to SaaS accounts, but is near impossible with the current setup.
Thanks,
Derek