Page History
...
OSLC Configuration Management support makes Teamwork Cloud OSLC services configuration-aware. This enables Teamwork Cloud resource discovery at the branch or tagged commit levels. The entry point for discovery of OSLC Configuration Management services is via the <oslc_config:cmServiceProviders> property. Teamwork Cloud concepts map to OSLC Configuration Management concepts in the following way:
| Teamwork Cloud concept | OSLC Configuration Management concept |
|---|---|
| Cameo Model (.Master Resource) | Component |
| Branch | Stream |
| Tagged Commit | Baseline |
| Used Project (Branch) | Contribution of a Stream to a Stream |
OAuth 1.0a authentication
...
OAuth 1.0a requires consumer key and secret to be known before starting the authentication process flow. These can be created through Teamwork Cloud Admin as described in Managing OAuth consumer client keys.
Alternatively, a pair of consumer key and secret can be generated manually via a service exposed in the root services document. The following HTTP POST request should be made to a consumer key generation service (jfs:oauthRequestConsumerKeyUrl):
...
Note, that keys generated following this approach will still need to be approved by an administrator through Teamwork Cloud Admin.