How to include custom authorization headers while connecting?

aws-amplify / aws-sdk-android

AWS SDK for Android. For more information, see our web site:

https://docs.amplify.aws

Other

1.03k stars 550 forks source link

How to include custom authorization headers while connecting? #429

Closed sunnymopada closed 4 years ago

sunnymopada commented 6 years ago

To help us solve your problem better, please answer the following list of questions.

What service are you using? AWS IOT
In what version of SDK are you facing the problem? 2.6.7
Is the issue limited to Simulators / Actual Devices? Both
Can your problem be resolved if you bump to a higher version of SDK? No
Is this problem related to specific Android/OS version? No
Can you give us steps to reproduce with a minimal, complete, and verifiable example? Please include any specific network conditions that might be required to reproduce the problem.

This is not an issue. We came to know that we can add custom authorization headers while connecting to aws iot broker at https://docs.aws.amazon.com/iot/latest/developerguide/custom-auth.html. So is there any snippet or reference to how to use them in android and ios?

rohandubal commented 6 years ago

Hello,

I have added this as a feature request in our backlog and have submitted it to the team for prioritization. I do not have specific timeline that I can share at this point. We will let you know, either on this thread, or through a forum announcement when the feature is released in the SDK.

Thanks, Rohan

iamtonny commented 5 years ago

Hi, do you have any news about custom authentication for android and ios sdk??? When it can be implemented (month, half-year, year) ?? Thanx

desokroshan commented 5 years ago

@iamtonny We are currently working on this request. I cannot share a specific timeline but I will update this thread once the feature has been released.

j0bro commented 5 years ago

I am currently working on a big project where this would be very helpful; the SDK documentation claims it allows for setting the custom authorization headers, but the implementation is only present in the JS SDK. In this forum thread there is a post by user vita1ii who created a patch on the Paho MQTT client which is embedded in the AWS Android SDK. Note that I am only assuming this functionality is also lacking from the iOS SDK, I am just following what was said above here. @desokroshan @kvasukib

mutablealligator commented 5 years ago

@j0bro We are waiting on Paho to release this fix so we could take a dependency on the version that has the fix. However for iOS SDK, we did not have any limitation, so we have this feature working for iOS: https://aws-amplify.github.io/docs/ios/pubsub#custom-authentication

SandyRagaie commented 5 years ago

I am working on Android project now and this feature request blocks a main functionality in the application, is there any known work around we can do to overcome this until aws sdk is released?

desokroshan commented 5 years ago

@SandyRagaie Thanks for reaching out. Supporting custom Auth in Android SDK needs paho version 1.2.1 which causes regression and breaks the SDK https://github.com/eclipse/paho.mqtt.java/issues/345. I will look into possible workarounds and provide an update soon as I can.

cmbaykal commented 4 years ago

Hi. I saw the new release. I wonder when the custom auth is added to AWS SDK ?

mutablealligator commented 4 years ago

@cmbaykal This is still in our backlog for prioritization. We will let you know through this issue when the changes are being released.

cagriyilmaz commented 4 years ago

Hi @desokroshan @kvasukib, do you have any news about custom authentication feature for android sdk?

desokroshan commented 4 years ago

SDK supports custom authentication starting from version 2.16.8. Please refer to the documentation for more details regarding its usage : https://docs.amplify.aws/sdk/pubsub/working-api?platform=android#custom-authentication

Please note that the latest versions (2.16.1 and above) of SDK/custom-auth feature cannot currently be used on Android API levels lower than 24. This is due to bug a in Paho and release with a fix is soon likely to follow. Please refer to https://github.com/aws-amplify/aws-sdk-android/issues/1259 for more details.