| Standards for Technology in Automotive Retail |
| Home - News Feed

13.5. STAR Transport Guidelines - Testing Checklist
Prev | Chapter 13. STAR Transport Testing | Next

## 13.5. STAR Transport Guidelines - Testing Checklist

Section | # | Requirement | Y/N/NA
1. Transport Introduction | 1 | Implementations MUST adhere to STAR data, transport and infrastructure requirements |
| 2 | STAR ebMS conformant implementations MUST be conformant to ebMS version 2.0 |
| 3 | STAR Web Services Implementations MUST be compliant to the WS-I Basic Profile 1.0. |
| 4. | STAR Web Services Implementations MUST support SOAP 1.1 |
| 5 | STAR Web Services Implementations MUST support WS-I Basic Security Profile 1.0 |
| 6 | STAR Web Services Implementations MUST support WS-ReliableMessaging 1.1 [Note 1] |
| 7 | STAR Web Services Implementations MUST support WS-Addressing 1.0 [Note 1] |
4. Message Level Security | 8 | Receiver MUST identify sender based on the to party name / URL or based on a security token |
| 9 | Receiver MUST authenticate a sender based on a security token |
| 10 | If present in message, digital certificates MUST be encrypted [Note 2 ] |
| 11 | Senders MUST take steps to ensure encryption of Password |
6. Auditing | 12 | Logging systems MUST be able to export information using UTC format (not local time) |
| 13 | Messages opened & or repackaged by intermediaries MUST have new Message IDs generated |
| 14 | Logged data MUST be made available upon request |
| 15 | Timestamps in messages in transit MUST be compliant to XMLSchema Datetime & be UTC/GMT format without offsets |
| 16 | Application generated MessageIDs MUST be globally unique |
| 17 | Application generated MessageIDs MUST include Company Name in domain format, Service Identifier and a locally unique ID |
| 18 | If the application does not generate a MessageID it MUST be generated by the Transport system |
| 19 | Transport generated MessageIDs MUST be globally unique |
| 20 | Logging systems MUST be capable of storing, displaying & being queried on key fields which MUST include Metadata, time sent or received, MessageID, From Party, To Party, Hostname of message sender, Activity, |
7. Performance | 21 | There MUST be a way to express that a payload is compressed before a receiver attempts to process payload |
9. Collaboration | 22 | All business partners and solutions MUST support asynchronous messaging |
| 23 | All business partners and solutions MUST support synchronous messaging |
10. Internet Connectivity | 24 | STAR Partner internet connections MUST allow for support of TCP/IP and HTTPs |
| 25 | STAR solutions MUST allow for support of internet addressable and non-addressable endpoints |
| 26 | STAR REQUIRES support for an internet connection and HTTP, HTTPs, TCP/IP, SOAP |
11. Registry | 27 | Discovery standards MUST be non-proprietary |
| 28 | Registries MUST support Service Transparency |
| 29 | Registries MUST support Location Transparency |
| 30 | Registries MUST support management of multiple versions of Services |

Checklist Notes:

1. Enter “NA” if this cannot be implemented due to product unavailability. This is a STAR Level 2 requirement, STAR Level 1 implementations should enter NA.

2. Although common practice may be to explicitly encrypt digital certificates, the more common practice of base64 encoding or passing digital certificates in the clear is not conformant to STAR guidelines.

Prev | Up | Next
13.4. How to Use the STAR Checklists | Home | Appendix A. Resources / References