Rename konnectd to IDP

docs/ocis/flow-docs/login-flow.md

@@ -44,7 +44,7 @@ sequenceDiagram
         Note over client, idp: GET /authorize?<br>response_type=code<br>&scope=openid%20profile%20email<br>&client_id=s6BhdRkqt3<br>&state=af0ifjsldkj<br>&redirect_uri=https%3A%2F%2Fclient.example.org%2Fcb HTTP/1.1<br>Host: server.example.com
         Note over user, idp: 3. Authorization Server Authenticates the End-User.
         Note over idp,ldap: Either an IdP already exists or a new one is introduced. Since we are not yet using oidc discovery we can only use one IdP.
-        alt all users managed by konnectd/ocis
+        alt all users managed by idp/ocis
             idp->>+glauth: LDAP query/bind
             glauth->>+graph: GET user with Basic Auth<br>GraphAPI
             graph->>+accounts: internal GRPC

docs/ocis/flow-docs/request-flow.md

@@ -28,7 +28,7 @@ sequenceDiagram
         Note over client,proxy: What is in a bearer token? <br> The spec recommends opaque tokens. <br> Treat it as random byte noise.
         Note over client,proxy: the proxy MUST authenticate users <br> using ocis-accounts because it needs <br> to decide where to send the request
         %% Mention introspection endpoint for opaque tokens
-        %% konnectd uses jwt, so we can save a request
+        %% idp uses jwt, so we can save a request
         %% either way the token can be used to look up the sub and iss of the user
 
             %% or is token check enough?