-
Key: GEMS13-3
-
Legacy Issue Number: 18313
-
Status: closed
-
Source: Amergint Technologies ( Rob Andzik)
-
Summary:
Authentication of a GEMS user is loosely defined in the specification.
This should be clarified and include a better definition of how
credentials are passed in, what is the roll (if any) of SSL and
similar transports, and how do proxies handle authentication. In
particular, how does a GEMS user grab control of a system without
creating a race condition. -
Reported: GEMS 1.2 — Thu, 13 Dec 2012 05:00 GMT
-
Disposition: Resolved — GEMS 1.3
-
Disposition Summary:
Add a multiplicity attribute to the ParameterSetDefType declaration to the GEMS_Device file, where it was omitted.
-
Updated: Fri, 6 Mar 2015 20:58 GMT