expirationTime from the CreateStageResponse in ivsrealtime is always null

[brian2197]

Describe the bug

Hi,

I am trying to integrate my service with AWS IVS real time streaming. The response from the stage creation CreateStageResponse does not populate the expirationTime property. i.e. response.participantTokens().getFirst().expirationTime() is always null. I have tried populating the duration of ParticipantTokenConfiguration and also tried leaving it as default (720) but it still does not populate the expirationTime property in the response.

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

I expect the expirationTime to be currentTime + duration

Current Behavior

expirationTime is always null

Reproduction Steps

try to create a stage using the SDK with a participant token - i.e. have the ParticipantTokenConfiguration setup. Inspect the response - CreateStageResponse

Possible Solution

No response

Additional Information/Context

currentTime + duration

AWS Java SDK version used

2.33.11

JDK version used

21.0.2

Operating System and version

MacOS Version 14.6

[bhoradc]

Hi @brian2197,

Thank you for reporting this issue with the expirationTime field returning null in the IVS Real-Time CreateStageResponse.

I see this as a service-level issue , not a problem with the Java SDK. I validated the same with AWS CLI as well.

In AWS CLI, it omits the expirationTime field entirely from the response.

The duration field is returned correctly in the response (returns the specified value). But if not supplied, returns null in Java SDK and gets omitted in AWS CLI.

I will reach out to the IVS service team internally to investigate the issue. Will post here again once I hear back from the team.

Thank you for bringing this to our attention. Documenting the AWS SDK for Java and AWS CLI minimal reproducible code sample below.

AWS for Java (v2.33.11)

import software.amazon.awssdk.services.ivsrealtime.IvsRealTimeClient;
import software.amazon.awssdk.services.ivsrealtime.model.*;

public class IvsRealtimeIssueReproduction {
    
    public static void main(String[] args) {
        IvsRealTimeClient client = IvsRealTimeClient.builder().build();

        ParticipantTokenConfiguration tokenConfig = ParticipantTokenConfiguration.builder()
                .duration(840)
                .build();

        CreateStageRequest request = CreateStageRequest.builder()
                .name("test-stage**")
                .participantTokenConfigurations(tokenConfig)
                .build();
        
        CreateStageResponse response = client.createStage(request);

        System.out.println("Stage ARN: " + response.stage().arn());
        System.out.println("Stage Name: " + response.stage().name());

        if (!response.participantTokens().isEmpty()) {
            for (int i = 0; i < response.participantTokens().size(); i++) {
                ParticipantToken token = response.participantTokens().get(i);
                System.out.println("Token " + (i + 1) + ":");
                System.out.println("  Duration: " + token.duration());
                System.out.println("  Expiration Time: " + token.expirationTime());
            }
        } else {
            System.out.println("No participant tokens returned");
        }
        client.close();
    }
}

AWS CLI (v2.27.49)

aws ivs-realtime create-stage \
  --name "test-stage**" \
  --participant-token-configurations '[{"duration": 840}]'

Regards,
Chaitanya

[brianRPhilip2197]

Hi @bhoradc ,

Thanks for getting back and looking into this!

I just also would like to bring up that I think the duration should return 720 (default) if there isn't one provided. As per the documentation that is the default value: https://docs.aws.amazon.com/ivs/latest/RealTimeAPIReference/API_ParticipantTokenConfiguration.html

Could you also help bring this up with the IVS service team internally? I would expect both duration and expiration time to never be null technically since it has a default value (i.e. if the ParticipantTokenConfiguration is configured in the request).

Let me know if I am mistaken here and this should infact both (duration and expirationTime) be null if the duration is null/not defined in the request.

Regards,
Brian

[bhoradc]

Hi @brian2197

Indeed, I saw the problem with duration as well, hence I mentioned about the impacted scenario.

I have submitted an internal ticket to the service team, will post here once I hear back from them.

Regards,
Chaitanya

[bhoradc]

Hi @brian2197

Service team has fixed the reported issue for duration and expirationTime fields. I have validated the fix works fine in Java SDK and AWS CLI. Kindly review at your end and let us know if you are good with it.

Regards,
Chaitanya

[brian2197]

Hi @bhoradc

I have confirmed the fix works! thank you for looking into this for me!

Regards,
Brian

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.