forked from device-management-toolkit/mps
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathswagger.yaml
More file actions
3318 lines (3294 loc) · 103 KB
/
swagger.yaml
File metadata and controls
3318 lines (3294 loc) · 103 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
openapi: 3.0.3
info:
version: 2.22.3
title: Management Presence Server (MPS) API
license:
name: Apache 2.0
url: https://www.apache.org/licenses/LICENSE-2.0.html
description: |
Open AMT Cloud Toolkit supports MPS API methods for authorization, user authentication, device-specific actions, such as power actions, and general device information.
For direct connection to MPS:
* MPS Format of URI: `{{protocol}}://{{host}}:{{port}}/api/v1/{{MPS API}}`
* Example URI for Authorize: [https://example.site.com:3000/login/api/v1/authorize]()
When running behind the Kong API proxy, prepend the following prefixes to the URI:
Kong prefixes:
* `/mps/login` for POST authorize method, `/mps` for GET authorize redirection method
* `/mps/ws` for websocket routes
* `/mps` for all other routes, including GET authorize/redirection method
For connection through Kong:
* MPS Format of URI: `{{protocol}}://{{host}}/{{Kong Prefix}}/api/v1/{{MPS API}}`
* Example URI for Authorize: [https://example.site.com/mps/login/api/v1/authorize]()
servers:
# Added by API Auto Mocking Plugin
- description: SwaggerHub API Auto Mocking
url: https://virtserver.swaggerhub.com/rbheopenamt/mps/2.22.0
security:
- BearerAuth: []
tags:
- name: Auth
description: User Authentication
- name: AMT
description: Device-Specific, Out-of-Band Actions
- name: Devices
description: Device Information
paths:
/api/v1/authorize:
post:
summary: Generate JWT Token for Authentication
description: |
Generates a JWT token that can be used for authentication to both MPS and RPS APIs. [Learn more about JWT](https://jwt.io/introduction).
**If using Kong**, make sure to use the prefix `/mps/login`
tags:
- Auth
requestBody:
description: Payload with username and password
required: true
content:
application/json:
schema:
required:
- username
- password
properties:
username:
type: string
password:
type: string
responses:
401:
description: 'Incorrect Username and/or Password'
200:
description: 'Success'
content:
application/json:
schema:
properties:
token:
type: string
/api/v1/authorize/redirection/{guid}:
get:
summary: Issue Short-lived Bearer Token for Redirection Sessions
description: |
Authenticate Redirection (KVM or SOL) sessions between the management console and MPS to allow only authenticated and authorized users to initiate.
**If using Kong**, make sure to use the prefix `/mps`, **NOT** `/mps/login`. Authorize Redirection does not use the login route.
tags:
- Auth
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
responses:
200:
description: 'Success'
content:
application/json:
schema:
properties:
token:
type: string
/api/v1/amt/log/audit/{guid}:
get:
summary: Return Intel® AMT Audit Log
description: Returns Intel® AMT Audit Log data in blocks of 10 records for a specified guid. Reference [AMT SDK](https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm?turl=WordDocuments%2Freadingtheauditlog.htm) for definition of property return codes.
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
- name: startIndex
in: query
description: number of items to skip
example: "startIndex=0"
required: false
schema:
type: integer
minimum: 0
default: 0
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/AuditLogResponse'
/api/v1/amt/log/event/{guid}:
get:
summary: Return Intel® AMT Event Log
description: Return sensor and hardware event data from the Intel® AMT event log. Reference [AMT SDK](https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm?turl=HTMLDocuments%2FWS-Management_Class_Reference%2FAMT_EventLogEntry.htm) for definition of property return codes.
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
# - name: startDate
# in: query
# description: Start date of log to retrieve
# required: true
# example: "2019-04-11"
# schema:
# type: string
# - name: endDate
# in: query
# description: End date of log to retrieve
# required: true
# example: "2019-04-18"
# schema:
# type: string
# - name: logsPerPage
# in: query
# description: Number of logs to return for this page
# required: true
# example: 10
# schema:
# type: number
# - name: page
# in: query
# description: Page of logs to retrieve
# required: true
# example: 5
# schema:
# type: number
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/EventLogResponse'
/api/v1/amt/version/{guid}:
get:
summary: Return Intel® AMT Version
description: Retrieves hardware version information for Intel® AMT and the current activation state.
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/AMTVersionResponse'
/api/v1/amt/generalSettings/{guid}:
get:
summary: Return Intel® AMT General Settings
description: Retrieve the Intel® AMT general settings.
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/GeneralSettingsResponse'
/api/v1/amt/hardwareInfo/{guid}:
get:
summary: Return Hardware Information
description: Retrieve hardware information such as processor or storage.
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/HardwareInfoResponse'
/api/v1/amt/features/{guid}:
post:
summary: Set Intel® AMT Features
description: Enable/Disable Intel® AMT User Consent, Redirection, KVM, SOL, IDE-R and OCR features.
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
requestBody:
description: Payload to set AMT Features
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/SetAMTFeaturesRequest'
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/SetAMTFeaturesResponse'
get:
summary: Return Intel® AMT Features
description: |
Retrieves the current Intel® AMT Enable/Disable state for User Consent, Redirection, KVM, SOL, IDE-R and One Click Recovery (OCR).
`optInState` refers to the current Opt In State if the device has User Consent enabled. Valid values:
- 0 (Not Started) - No sessions in progress or user consent requested
- 1 (Requested) - Request to AMT device for user consent code successful
- 2 (Displayed) - AMT device displaying user consent code for 300 seconds (5 minutes) before timeout by default
- 3 (Received) - User consent code was entered correctly, a redirection session can be started. Will expire after 120 seconds (2 minutes) and return to State 0 if no active redirection session (State 4)
- 4 (In Session) - Active redirection session in progress
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
required: true
schema:
type: string
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/GetAMTFeaturesResponse'
/api/v1/amt/alarmOccurrences/{guid}:
post:
summary: Set new Alarm Clock Occurence
description: Create a new Alarm Clock occurence to wake device for AMT device.
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
requestBody:
description: Payload to set new Alarm Clock
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/SetAlarmClockRequest'
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/SetAlarmClockResponse'
get:
summary: Return Alarm Clock Occurences
description: Retrieves all of the current Alarm Clock occurences for the device.
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
required: true
schema:
type: string
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/GetAlarmClockResponse'
delete:
summary: Delete Alarm Clock Occurence
description: |
Delete named Alarm Clock occurence from the device.
**IMPORTANT**<br>
**The DELETE method DOES REQUIRE a Request Body:**<br><br>
**{<br>
 "Name": "string"<br>
}**<br>
Note: Unfortunately, SwaggerHub and OpenAPI 3.0 spec does not allow DELETE requests to have a Request Body for documentation. This has changed for OpenAPI 3.1 although SwaggerHub has not completed their migration from 3.0 -> 3.1 . We apologize for this deviation from the other documentation, please bear with us as we eagerly await the SwaggerHub update. Thank you!
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/DeactivateResponse'
404:
description: 'Alarm Instance does not exist'
content:
application/json:
schema:
$ref: '#/components/schemas/DeleteAlarmErrorResponse'
500:
description: 'Internal Server Error'
/api/v1/amt/power/state/{guid}:
get:
summary: Return Current Device Power State
description: |
Retrieve current power state of Intel® AMT device, returns a number that maps to a device power state.
Possible power state values:
* 2 = On - corresponding to ACPI state G0 or S0 or D0
* 3 = Sleep - Light, corresponding to ACPI state G1, S1/S2, or D1
* 4 = Sleep - Deep, corresponding to ACPI state G1, S3, or D2
* 6 = Off - Hard, corresponding to ACPI state G3, S5, or D3
* 7 = Hibernate (Off - Soft), corresponding to ACPI state S4, where the state of the managed element is preserved and will be recovered upon powering on
* 8 = Off - Soft, corresponding to ACPI state G2, S5, or D3
* 9 = Power Cycle (Off-Hard), corresponds to the managed element reaching the ACPI state G3 followed by ACPI state S0
* 13 = Off - Hard Graceful, equivalent to Off Hard but preceded by a request to the managed element to perform an orderly shutdown
OSPowerSavingState values mapping:
* 0 = UNKNOWN
* 1 = UNSUPPORTED
* 2 = FULL_POWER
* 3 = OS_POWER_SAVING
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/PowerStateResponse'
/api/v1/amt/power/capabilities/{guid}:
get:
summary: Return Available Power Actions
description: View what OOB power actions are available for that device.
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/PowerCapabilitiesResponse'
/api/v1/amt/power/action/{guid}:
post:
summary: Perform OOB Power Action (1 to 99)
description: |
Perform an OOB power actions. Execute a [GET /power/capabilities/{guid}](#/AMT/get_api_v1_amt_power_capabilities__guid_) call first to get the list of available power actions. See [AMT Power States](https://device-management-toolkit.github.io/docs/2.27/Reference/powerstates/) for ALL potential power actions. <br /><br />
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
requestBody:
description: |
**Standard Power Actions:**
* 2 = Power up/on
* 5 = Power cycle
* 8 = Power down/off
* 10 = Reset
* 500 = OS to full power
* 501 = OS to power saving
**Power Actions Requiring Intel LMS:**
* 4 = Sleep
* 7 = Hibernate
* 12 = Soft power down/off
* 14 = Soft reset
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/PowerActionRequest'
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/PowerActionResponse'
/api/v1/amt/power/bootOptions/{guid}:
post:
summary: Perform OOB Power Action (100+)
description: |
Perform an OOB power actions numbered 100+. Execute a [GET /power/capabilities/{guid}](#/AMT/get_api_v1_amt_power_capabilities__guid_) call first to get the list of available power actions. See [AMT Power States](https://device-management-toolkit.github.io/docs/2.27/Reference/powerstates/) for ALL potential power actions.
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
requestBody:
description: |
Possible Power Actions:
* 100 = Power up to BIOS settings
* 101 = Reset to BIOS settings
* 105 = Reset to HTTPS Boot
* 106 = Power on HTTPS Boot
* 107 = Reset to PBA Boot
* 108 = Power on to PBA Boot
* 109 = Reset to Win-Re
* 110 = Power up to Win-Re
* 202 = Reset to IDE-R CD-ROM
* 203 = Power on to IDE-R CD-ROM
* 400 = Reset to PXE
* 401 = Power on to PXE
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/PowerActionRequest'
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/PowerActionResponse'
/api/v1/amt/power/bootSources/{guid}:
get:
summary: Request for boot source settings information
description: Boot Source settings information for OCR(HTTPs, PBA and Win-Re)
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/BootSourcesResponse'
/api/v1/amt/userConsentCode/{guid}:
get:
summary: Request an user consent code on client device
description: If optInState is 0, it will request for a new user consent code
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/UserConsentResponse'
post:
summary: Send user consent code
description: Send the user consent code displayed on the client device
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
requestBody:
description: ''
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/UserConsentRequest'
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/UserConsentResponse'
/api/v1/amt/userConsentCode/cancel/{guid}:
get:
summary: Cancel user consent code
description: Cancel six digit user consent code previously generated on client device
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/UserConsentResponse'
/api/v1/amt/deactivate/{guid}:
delete:
summary: Deactivate AMT over CIRA
description: Deactivate an AMT device using the CIRA channel with MPS rather than RPS RPC.
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/DeactivateResponse'
404:
description: 'Device does not exist'
content:
application/json:
schema:
$ref: '#/components/schemas/DeleteErrorResponse'
500:
description: 'Internal Server Error'
/api/v1/amt/certificates/{guid}:
get:
summary: Get device certificates
description: Retrieve all certificates associated with the specified AMT device
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/GetCertificatesResponse'
404:
description: 'Device not found'
content:
application/json:
schema:
$ref: '#/components/schemas/DisconnectErrorResponse'
500:
description: 'Internal server error'
post:
summary: Add device certificates
description: Add new certificates to the specified AMT device
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
requestBody:
description: Certificate data to add
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/AddCertificatesRequest'
responses:
200:
description: 'Certificates added successfully'
content:
application/json:
schema:
$ref: '#/components/schemas/AddCertificatesResponse'
400:
description: 'Invalid certificate format (not valid DER or PEM)'
404:
description: 'Device not found'
content:
application/json:
schema:
$ref: '#/components/schemas/DisconnectErrorResponse'
500:
description: 'Internal server error'
/api/v1/amt/kvm/displays/{guid}:
get:
summary: Get number of displays information from AMT
description: Retrieve all display information of KVM from AMT
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/GetDisplaysResponse'
404:
description: 'Device not found'
content:
application/json:
schema:
$ref: '#/components/schemas/DisconnectErrorResponse'
500:
description: 'Internal server error'
put:
summary: Put the changed settings for KVM in AMT
description: Modify screen settings for KVM in AMT device
tags:
- AMT
parameters:
- name: guid
in: path
description: GUID of device
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
requestBody:
description: Screen Setting data to update
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/UpdateDisplaySettingsRequest'
responses:
200:
description: ''
content:
application/json:
schema:
$ref: '#/components/schemas/UpdateDisplaySettingsResponse'
404:
description: 'Device not found'
content:
application/json:
schema:
$ref: '#/components/schemas/DisconnectErrorResponse'
500:
description: 'Internal server error'
/api/v1/devices:
get:
summary: List All Known Devices
description: Lists all devices known to MPS.
tags:
- Devices
parameters:
- in: query
name: $count
required: false
schema:
type: boolean
description: If set to true, return `totalCount` of devices with `data` array of devices
- in: query
name: $skip
required: false
schema:
type: integer
description: The number of items to skip before starting to collect the result set
- in: query
name: $top
required: false
schema:
type: integer
description: The number of items to return
- in: query
name: friendlyName
description: Device friendly name to query for. Maximum length 255
example: 'friendlyName=myname'
required: false
schema:
type: string
- in: query
name: hostname
description: Device hostname to query for. Maximum length 255
example: 'hostname=mydevice'
required: false
schema:
type: string
- in: query
name: method
description: Specify a conditional operator 'AND' or 'OR' to fetch the records with given tags .
example: 'method=AND'
required: false
schema:
type: string
- in: query
name: status
description: Specify '0' to query for disconnected devices or specify '1' for connected devices. To return all devices, omit this query parameter.
example: 'status=1'
required: false
schema:
type: integer
- in: query
name: tags
description: Comma-delimited list of tags to query for
example: 'tags=NUC,Store #123'
required: false
schema:
type: string
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
oneOf:
- type: array
items:
$ref: '#/components/schemas/Device'
- $ref: '#/components/schemas/CountDevicesResponse'
500:
description: 'Internal server error'
post:
summary: Add New Device to MPS
description: Adds a new device to MPS. This call does not add the device credentials. In order for MPS to manage the device, a separate call to Vault must be made to add the credentials. For example, the Remote Provision Server (RPS) makes the call to Vault to add the AMT device credentials during activation of the AMT device.
tags:
- Devices
requestBody:
description: Payload to add AMT device to MPS
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/AddDevice'
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/AddDeviceResponse'
500:
description: 'Internal server error'
patch:
summary: Edit a Device
description: Edit a single device in the MPS. This call does not edit the AMT device credentials. To update these, a separate call to Vault must be made. For example, the Remote Provision Server (RPS) makes the call to Vault to add the AMT device credentials during activation of the AMT device.
tags:
- Devices
requestBody:
description: Payload to edit AMT device in MPS
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/EditDevice'
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/EditDeviceResponse'
500:
description: 'Internal server error'
/api/v1/devices/redirectStatus/{guid}:
get:
summary: Find Redirection State of Device by GUID
description: Retrieves boolean values for KVM, SOL, and IDER session states.
tags:
- Devices
parameters:
- name: guid
in: path
description: GUID of device to return
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
responses:
400:
description: 'Error in request. A list of errors will be returned'
404:
description: 'Device does not exist'
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/RedirectStatus'
500:
description: 'Internal server error'
/api/v1/devices/stats:
get:
summary: Return Count of All Devices by Connection Status
description: Retrieve the current count of all registered, connected, and disconnected devices.
tags:
- Devices
responses:
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/Stats'
/api/v1/devices/{guid}:
get:
summary: Find Device by GUID
description: Retrieves the device with a specific GUID and all device information from the database.
tags:
- Devices
parameters:
- name: guid
in: path
description: GUID of device to return
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
responses:
400:
description: 'Error in request. A list of errors will be returned'
404:
description: 'Device does not exist'
200:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/Device'
500:
description: 'Internal server error'
delete:
summary: Delete Device Information
description: Removes the device with a specific GUID and all device information from the database. This will prevent the device from connecting to MPS, even if the device has not yet been unprovisioned. Use the disconnect API after this call to remove a device and prevent it from reconnecting to the MPS.
tags:
- Devices
parameters:
- name: guid
in: path
description: GUID of device to return
example: 123e4567-e89b-12d3-a456-426614174000
required: true
schema:
type: string
- name: isSecretToBeDeleted
in: query
description: "Delete device information from both the Database **AND Secret Storage**. Caution: This will delete the stored device passwords in Secret Storage."
example: isSecretToBeDeleted=true
schema:
type: boolean
responses:
404:
description: 'Device does not exist'
content:
application/json:
schema:
$ref: '#/components/schemas/DeleteErrorResponse'
204:
description: 'Successful operation'
content:
application/json:
schema:
$ref: '#/components/schemas/DeleteResponse'
500:
description: 'Internal server error'
/api/v1/devices/disconnect/{guid}:
delete:
summary: Disconnect Device
description: Forces a specified device to disconnect from the MPS. Device will reconnect again if it is able. To prevent reconnection, first [delete the device information](#/Devices/delete_api_v1_devices__guid_) from MPS.