Announcements

SecurID® Discussions

Browse the SecurID discussion board to get product help and collaborate with other SecurID users.
LukeYang
Beginner
Beginner

Issue with Android 10

Jump to solution

Hi guys,

 

So here is my situation now, I am using OnePlus 7Pro with Android 10 open beta now. Previously when I was using the same device with Android 10 (updated from Android 9 directly), everything works like a charm. Yesterday, I did a factory reset on my phone, and when I re-installed RSA Token SecureID (version 2.6.1), it popped-up with the already knwon "Aeroplane Mode" issue. So I managed to donwload and installed the beta version of the App (version 2.7.0) from Play Store, and the new version solved the "Aeroplane Mode" issue. However, the issue now is when the IT support of my firm try to scan the QR code to import the token, the App simply did not responde. Any idea on how to solve this problem will much appreciated!

 

Note:

-When I was with IT Support, I believe only Camera premission was given to the App. Should I also give the Storage and Telephone premission to the App as well? 

-I have asked my IT Support, and they said they currently can only import the token via QR Scan. So I did not know if URL import works. 

 

Thanks again and hope there is a solution for this problem. 

 

Luke

Labels (1)
0 Likes
1 Solution

Accepted Solutions

Hi Steven, Thanks for replying. After several attempts with my IT Support, I have managed to solve the problem - it turns out the issue is with my firm's WiFi.. By changing to non-firm's network (I tried WiFi connection, somehow it is weird that mobile connection/4G did not work out), I have successfully imported the token. 

View solution in original post

3 Replies
StevenSpicer
Valued Contributor Valued Contributor
Valued Contributor

I haven't tried the 2.7 beta, but my 2.6.1 token app has camera, phone and storage permissions.

0 Likes

Hi Steven, Thanks for replying. After several attempts with my IT Support, I have managed to solve the problem - it turns out the issue is with my firm's WiFi.. By changing to non-firm's network (I tried WiFi connection, somehow it is weird that mobile connection/4G did not work out), I have successfully imported the token. 

That's pretty common -- lots of firms really lock down their internal wifi.

0 Likes