Skip to main content
summaryrefslogtreecommitdiffstats
blob: 0697b0f9b5531199ed29d800c861792caa81e7f1 (plain) (blame)
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
////
******************************************************************************
* Copyright © 2018 Mettenmeier GmbH.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Eclipse Public License v1.0
* which accompanies this distribution, and is available at
*
*     http://www.eclipse.org/legal/epl-v10.html
*
******************************************************************************
////
= openKonsequenz "StandbyPlanning" - documentation for administration
:Date: 2019-01-10
:Revision: 1

What is needed?
    
    * KeyCloak
    * Postgres
    * oK-Auth-Application
        ** portalFE
        ** portal
        

=== KeyCloak[[KeyCloak]]

You need to have a running KeyCloak. All the user of the application standbyplanning have to be well-kept in KeyCloak. 
For minimal access use the role 
*BP_Leseberechtigte*.

Ensure you have configured a client. 


.Client
[source]
	Client ID:                      standbyplanning
	Name :                          Bereitschaftsplanung
	Enabled:                        true
	Consent Required:               false
	Client Protocol:                openid-connect
	Access Type :                   public
    Standard Flow Enabled:          true
    Implicit Flow Enabled:          false
    Direct Access Grants Enabled:   true
    Authorization Enabled:          false
    Root URL:               
    Valid Redirect URIs:            http://localhost:8080/*
    Base URL:                       http://localhost:8080/spfe/
    Admin URL:   
    Web Origins:                    *

Ensure you have configured the roles.
	
.Roles
[source]
    Role Name:              BP_Admin
    Scope Param Required:   false
    Composite Roles:        false
----
	Role Name:              BP_Gruppenleiter
	Scope Param Required:   false
	Composite Roles:        false
----	
	Role Name:              BP_Leseberechtigte
	Scope Param Required:   false
	Composite Roles:        false
----	
	Role Name:              BP_Sachbearbeiter
	Scope Param Required:   false
	Composite Roles:        false
	
	
=== Postgres

A postgres database and a user have to be created. After that all the needed tables and sequences will be genreated bei the "Standby Planning" backend (spbe). For more details see ../howto/config.adoc


=== oK-Auth-Application
The auth&auth application is available from the oK Eclipse Git. Refere to https://git.eclipse.org for getting the code and more installation details.  
For more details how to configure the Standby Planning Application in the Auth-Application see ../howto/config.adoc

Back to the top