WSO2 device agent gives authentication failure notification in some time gap.

[prashantkt10]

I'm using WSO2 IOT open source version. The mobile device agent automatically gives authentication failure notification and asks to re-enter login credentials. I've started WSO2 IOT server on my system and installed WSO2 IOT device agent from QR code URL, the mobile device and WSO2 IOT server both are on LAN so there is no delay in network calls and also there is no firewall or anything which may disturb the communication. Am I missing something or Its a bug ?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity.

[Stjin]

Same problem here.

[MikPoik]

Same problem here, after a while Android device gives authentication error, please sign in again.

[rgmalagon]

i have the same issue, hot can i fix

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity.

[bouroy]

I have the same issue with 3.3.0

[GingerM]

I have the same issue on 3.3.0, on investigating the mobile device agent i found that the call to refresh the token returns 400

resolved by removing the scope=PRODUCTION parameter from the refresh token request (RefreshTokenHandler, line 107)

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity.

[monta9]

same problem always send notification which i must put username and password how can i regester my username and password for ever

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity.

[osmaney]

Same problem always send notification which i must put username and password.

You have found the solution for this problem? Thanks

[monta9]

Yes I found a solution

Le lun. 3 juin 2019 à 12:19, osmaney notifications@github.com a écrit :

Same problem always send notification which i must put username and password.

You have found the solution for this problem? Thanks

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/wso2/product-iots/issues/1848?email_source=notifications&email_token=AKLOM43X3X7IAPJTCRTPPYTPYTV3XA5CNFSM4FML2ORKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWY62NA#issuecomment-498199860, or mute the thread https://github.com/notifications/unsubscribe-auth/AKLOM4YPWIVVZMXR4DFWEFTPYTV3XANCNFSM4FML2ORA .

[osmaney]

Good.. And can tell me how do you do?

Thanks

[monta9]

You work with http or https

Le lun. 3 juin 2019 à 14:44, osmaney notifications@github.com a écrit :

Good.. And can tell me how do you do?

Thanks

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/wso2/product-iots/issues/1848?email_source=notifications&email_token=AKLOM42B25RP4W7474AZAN3PYUG3XA5CNFSM4FML2ORKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWZI3HI#issuecomment-498240925, or mute the thread https://github.com/notifications/unsubscribe-auth/AKLOM463O6LONOV43R45UDDPYUG3XANCNFSM4FML2ORA .

[osmaney]

i work with https: 9443 port

[monta9]

No I mean when you enroll a device with what port number you use 8243 or 8280

Le lun. 3 juin 2019 à 15:32, osmaney notifications@github.com a écrit :

i work with https: 9443 port

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/wso2/product-iots/issues/1848?email_source=notifications&email_token=AKLOM44MMS5VQQ7JB2QQMY3PYUMOXA5CNFSM4FML2ORKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWZNA2A#issuecomment-498258024, or mute the thread https://github.com/notifications/unsubscribe-auth/AKLOM47PQQTNK7TAOAKXPRLPYUMOXANCNFSM4FML2ORA .

[osmaney]

I use 8280 port

[monta9]

That's the problem you must use a certificate to ensure a https communication. With https you will use 8243 port number and then it's done

Le lun. 3 juin 2019 à 15:51, osmaney notifications@github.com a écrit :

I use 8280 port

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/wso2/product-iots/issues/1848?email_source=notifications&email_token=AKLOM45ZGFB7YGXMJGPRJ6TPYUOXLA5CNFSM4FML2ORKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWZO3EI#issuecomment-498265489, or mute the thread https://github.com/notifications/unsubscribe-auth/AKLOM436TVXTSEHLN6EBLPLPYUOXLANCNFSM4FML2ORA .

[monta9]

For more questions I can explain to you by what's up

Le lun. 3 juin 2019 à 16:00, boukrain montassar < montassar.boukrain@gmail.com> a écrit :

That's the problem you must use a certificate to ensure a https communication. With https you will use 8243 port number and then it's done

Le lun. 3 juin 2019 à 15:51, osmaney notifications@github.com a écrit :

I use 8280 port

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/wso2/product-iots/issues/1848?email_source=notifications&email_token=AKLOM45ZGFB7YGXMJGPRJ6TPYUOXLA5CNFSM4FML2ORKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWZO3EI#issuecomment-498265489, or mute the thread https://github.com/notifications/unsubscribe-auth/AKLOM436TVXTSEHLN6EBLPLPYUOXLANCNFSM4FML2ORA .

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity.