View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
001046610000-012: DiscoverySpecpublic2025-08-11 07:372025-09-25 09:34
ReporterHock, Christian Assigned ToRandy Armstrong  
PriorityhighSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version1.05.06 RC1 
Target Version1.05Fixed in Version1.05.06 
Summary0010466: Clarification about '7.10.3 ServerConfigurationType -> InApplicationSetup' and 'ApplicationInstance Certificate'
Description

Currently the '7.10.3 ServerConfigurationType -> InApplicationSetup' property usage is described only for Server, but not for '7.10.14 ApplicationConfiguration'.

Spec 1.05.06 RC1 states in '7.10.3 ServerConfigurationType':

  • If the InApplicationSetup Property is TRUE then the Server is in the application setup state described in G.2.

Spec 1.05.06 RC1 states in 'G.2 Application setup with the PushManagement':

  • It is good practice for a Client to always check the ServerState after creating a Session. If the ServerState is NoConfiguration then the Client should check the InApplicationSetup Property on the ServerConfiguration Object to confirm that the Server is in the application setup state.

Questions:

  • What is the expected ServerState when the Server is configured but not all Applications where the 'ApplicationType' is NOT Server?
  • What is the expected use of the 'InApplicationSetup' property when an Application has not yet been set up?
  • How can a GDS obtain information about the 'ApplicationInstance Certificate(s)' that have already been set up (previously) - e.g. from a previous GDS?
    • Currently, only the 'ApplicationInstance Certificate' for the Server can be read indirectly (via GetEndpoints), but there is no way to obtain it for Applications where the 'ApplicationType' is NOT Server.
TagsNo tags attached.
Commit Version1.05.06
Fix Due Date2025-09-15

Activities

Jim Luth

2025-08-12 16:15

administrator   ~0023226

We agreed that the section on "Push management for a Server" needs to be renamed "Push Management" and the two scenarios need to be explicitly described:

  1. Management of the directly connected Server.
  2. Management of Applications (Client(s) and Server(s)) indirectly via the connected Server acting as a proxy for the target Applications.

Randy Armstrong

2025-09-16 07:34

administrator   ~0023287

Made it clear how InApplicationSetup applies to managed Applications in 7.10.3, 7.10.14 and G.2.

Jim Luth

2025-09-25 09:34

administrator   ~0023354

Agreed to changes edited in F2F.

Issue History

Date Modified Username Field Change
2025-08-11 07:37 Hock, Christian New Issue
2025-08-12 16:15 Jim Luth Note Added: 0023226
2025-08-12 16:15 Jim Luth Assigned To => Randy Armstrong
2025-08-12 16:15 Jim Luth Status new => assigned
2025-08-12 16:16 Jim Luth Commit Version => 1.05.06
2025-08-12 16:16 Jim Luth Fix Due Date => 2025-09-15
2025-09-16 07:34 Randy Armstrong Status assigned => resolved
2025-09-16 07:34 Randy Armstrong Resolution open => fixed
2025-09-16 07:34 Randy Armstrong Note Added: 0023287
2025-09-25 09:34 Jim Luth Status resolved => closed
2025-09-25 09:34 Jim Luth Fixed in Version => 1.05.06
2025-09-25 09:34 Jim Luth Note Added: 0023354