Assigned
Status Update
Comments
be...@banked.com <be...@banked.com> #2
Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.
mm...@google.com <mm...@google.com>
be...@banked.com <be...@banked.com> #3
One more detail, Data Layer event calls from the watch to the phone (running Android 13) do work on if the listener is in an Activity or Fragment.
be...@banked.com <be...@banked.com> #4
Also, I'm seeing this message in the Logcat:
"2022-06-12 18:47:15.156 1841-4562/? W/PackageManager: Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER"
"2022-06-12 18:47:15.156 1841-4562/? W/PackageManager: Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER"
ti...@vestr.com <ti...@vestr.com> #5
Experiencing the same issues, please see my other report for any useful logs:
https://issuetracker.google.com/issues/235673375
Description
I would like to offload the TLS from the load balancer to something that can talk to cloud hsm, and perform the TLS termination
The hard requirements I have are:
Basically, I need to provide a certificate that my network is FIPS Level 3 validated, but think it is not possible on GCP right now, I would like to share an example which is from a competitor but it is what I would like to have. Would it be possible to run this scenario by the team responsible for KMS?
Do you know of any workaround that can do the TLS termination by checking a Private Key that is stored inside the Google HSM? Be it an nginx/ gce ingress / neg or otherwise?
Alternatively, would it be possible to use CMEK with the uploaded private certificate in google cert manager?
Kind Regards,