Closed ashokkkannan closed 4 years ago
Thanks for reporting this issue. If you use the web browser experience for OCI with non-ascii unicode characters, do the same operations failing here work from the browser?
Yes they work from oci web console , CLI and the go sdk (I didn't try other SDKs)
Thanks, we'll take a look
Can we get some updates on this issue please? As mentioned earlier this issue combined with #47 may lead to severe issues in production. Considering the oci regions we have, it may not be long before someone else also gets impacted.
Hi @ashokkkannan - we will take a look and get back to you
Hi @ashokkkannan This issue has been fixed with the latest release v2.9.0.
Requests failing with Authentication failure (http 401) when using non-ascii Unicode characters in the request. I tried it with few services and the behavior is the same. There seems to be some issue with the way SDK signs the requests. Note: I'm able to create the resource with name containing non-ascii Unicode characters using Console, oci-cli,oci-go-sdk just fine.
This issue combined with https://github.com/oracle/oci-ruby-sdk/issues/47 caused an outage in our production environment. I appreciate it if this issue can be prioritized.
Example:
Testing with Compute service:
Code:
Creating with normal characters (value of the
name
in the above code is set to "simple-instance"):Creating with non standard characters (value of the
name
in the above code is set to "Futbolín"):Testing with OKE service:
code:
Creating OKE cluster with normal character:(value of the
cluster_name
in the above code is set to "simple-cluster")Creating OKE cluster with non-standard character:(value of the
cluster_name
in the above code is set to "Futbolín")Way to reproduce the issue:
Try creating a compute instance(or any oci service instance) with a name that contains non-ascii Unicode characters(example: Futbolín).