How to get user token from Android

hungChun 0

Form the Microsoft Learn, I can't find how to get user's token of android.

Is there some method like below?

Why most examples just ask us to fill existed token, but not get the token form code?

            // Issue an access token with a validity of 24 hours and the "voip" scope for an identity
            //CommunicationUserIdentifier id = new CommunicationUserIdentifier(clientIdentity);
            Azure.Communication.CommunicationUserIdentifier id = new Azure.Communication.CommunicationUserIdentifier(clientIdentity);
            var tokenResponse = client.GetTokenAsync(id, scopes: new[] { CommunicationTokenScope.VoIP });

            // Get the token from the response
            this.clientToken = tokenResponse.Result.Value.Token;
           // var expiresOn = tokenResponse.Result.Value.ExpiresOn;

1 answer

brtrach-MSFT 15,176 Reputation points Microsoft Employee

2023-03-05T23:54:32.2833333+00:00

@hungChun We understand you would like more samples of how to obtain token's; specifically tokens on Android.

We have gone ahead and created the document feedback request and assigned it to the document author since this requires a larger rewrite of the document.

In the future, feel free to go ahead and create the document feedback request by following the steps to provide feedback at the bottom of the document(s).

You can track the request here. Please let us know if you have any questions or concerns.
Please sign in to rate this answer.
hungChun 0 Reputation points

2023-03-08T02:29:50.14+00:00

Thanks for the replay.

I have a project that need some android pads to communicate with central control room.

in most case the android pad make video calls to central control room, we want to save the recording file of video calls.

I searched for some solutions(SDKs) and decide to try the Azure communication service. I need to write code for android pad and desktop PC(central control room)

From the description it meets the need, but when I look into it and tried the SDK:

1.

the video call only support windows(UWP), and the SDK still in beta version, when I try that, It always crash when Android pad hang up the call. (maybe after remoteVideoStream.Stop();)

The SDK is not open source and didn't provide pdb file so I can't even debug it. the try catch not working and jump to unhandled exception(Win32 Error), it seems like the SDK is written in Unmanaged code? I tried to use try cath in every function and set break point, still not working.

private async void Call_OnVideoStreamsUpdatedAsync(object sender, RemoteVideoStreamsEventArgs args) { foreach (var remoteVideoStream in args.AddedRemoteVideoStreams) { await Dispatcher.RunAsync(Windows.UI.Core.CoreDispatcherPriority.Normal, async () => { RemoteVideo.Source = await remoteVideoStream.Start(); }); } try { foreach (var remoteVideoStream in args.RemovedRemoteVideoStreams) { remoteVideoStream.Stop(); } } catch (Exception ex) { int debug = 0; } }

The recording API only support Java and C#.

The video call API support Web, Android, IOS, window(C#). C# SDK is beta version and crash the app.

The token access API support C#, javascript, JAVA, python

I can't find a way to do my work(let android pad make video call to A desktop windows APP, record the video call and download the file.)

Android: can't get user token

C#(UWP): crash the app,

Website(javascript) as desktop APP: can't record the video call, and I'm not sure if it can be used in central control room.

As mentioned above, I have doubt that if the SDK can be used in production environment.

Could you give me some advices about it?

brtrach-MSFT 15,176 Reputation points Microsoft Employee

2023-03-08T02:38:12.0933333+00:00

Please see the doc author's comment below:

Hi Here is a link to Java (not Android) QuickStart for authentication. ACS currently does not have a dedicated Android Identity SDK, as the connection string required for the SDK should not be shared with the client application for security reasons.
https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/identity/access-tokens?tabs=windows&pivots=programming-language-java The tokens are essential for audio, video, chat, meetings, and telephony. Instead of repeating the same authentication code in all QuickStarts, we have decided to have single dedicated authentication QuickStart that is referred from chat and calling. I hope you find this information helpful. Let me know if there is anything else we can help with.

Regarding the recording API, it is currently only available in Java and C#. If you need to use it in a different language, you can try to use the REST API for recording. You can find more information about the REST API in the following link: https://docs.microsoft.com/en-us/azure/communication-services/how-to/recording-rest-api

In regard to the token access API, you can use the AcquireTokenInteractive method to get the token for the user. The scopes parameter enumerates strings that define the scopes for which a token is required. If the token is for Microsoft Graph, you can find the required scopes in the API reference of each Microsoft Graph API. In the reference, go to the "Permissions" section.

Regarding the use of the SDK in a production environment, it is currently in beta and might not be suitable for production use.

I think at this point, you are hitting multiple roadblocks and it would be best to put you in touch with a support engineer who can work one on one with you.

Can you please send an email to azcommunity@microsoft.com with the subject as ATTN: Bryan and in the body of the email please include your Azure subscription ID. Those two items are important otherwise I may not see the email come across. We look forward to hearing from you.

hungChun 0 Reputation points

2023-03-10T03:07:15.9033333+00:00

Thanks for the reply.

Its sad to hear that the SDKs is not ready to the paid services. The calling service is so good but SDKs and examples are not ready for it...

The core of communication service code is not open source, so it seems the Development Team can just depend on theirself. We need to find an available solution to complete the job. hope we can see the progress of these SDKs and examples in near future.
Sign in to comment