Date: Fri, 29 Mar 2024 08:21:14 +0100 (CET) Message-ID: <204468735.1636.1711696874119@nm-docs> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1635_798398362.1711696874119" ------=_Part_1635_798398362.1711696874119 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Teamwork Cloud adds OSLC s= upport and now exposes model element data following OSLC Architecture Manag= emenet (AM) (http://open-services.net/ns/am#) vocabulary. Alon= g with core OSLC services provided in Teamwork Cloud, this enables smooth i= ntegration with other OSLC-compatible tools by linking resources in Linked = Data fashion. Here are the key points behind current Teamwork Cloud OSLC pr= ovider implementation:
<?xml= version=3D"1.0" encoding=3D"UTF-8"?> <rdf:RDF=20 xmlns:oslc=3D"http://open-services.net/ns/core#" =09 =20 =09xmlns:oslc_am=3D"http://open-services.net/ns/am#" =20 =09xmlns:dc=3D"http://purl.org/dc/terms/" xmlns:dcterms=3D"http://purl.org/dc/terms/" =09 xmlns:rdf=3D"http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs=3D"http://www.w3.org/2000/01/rdf-schema#"> <rdf:Description rdf:about=3D"https://localhost:8111/oslc/am/b1acff2d-= 4396-4314-9dba-477d573ede16/50775427-bce2-4de4-b747-8ab82d294237"> <rdf:type rdf:resource=3D"http://open-services.net/ns/am#Resource"/&= gt; <oslc:serviceProvider rdf:resource=3D"https://localhost:8111/oslc/am= /b1acff2d-4396-4314-9dba-477d573ede16/services"/> <dcterms:modified rdf:datatype=3D"http://www.w3.org/2001/XMLSchema#d= ateTime">May 16, 2018 2:08:52 PM</dcterms:modified> <dcterms:identifier rdf:datatype=3D"http://www.w3.org/2001/XMLSchema= #string">50775427-bce2-4de4-b747-8ab82d294237</dcterms:identifier> <dcterms:title rdf:parseType=3D"Literal">Engine</dcterms:title= > </rdf:Description> </rdf:RDF>
Currently, querying services are not supported. Model data can = only be read through OSLC services and editing capabilities are not support= ed.
To ensure secure access to server resources via OSLC, OAuth 1.0a authent= ication protocol is used.
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 keys.
Alternatively, a pair of consumer key and secret can be generated manual=
ly 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):
{ "name": "consumerNameGoesHere", "secret": "OAuthSecretGoesHere" }
{ "key": "generatedConsumerKeyShouldBeHere" }
Note, that keys generated following this approach will still need to be = approved by an administrator through = Teamwork Cloud Admin console.