Debian Codegraph @

README

raw
1 # Setting up accounts-sso
2
3 Accounts-SSO is the framework we are using to store secrets (tokens, passwords)
4 and for storing Accounts (small pieces of information containing a name,
5 a provider, etc).
6
7 https://accounts-sso.gitlab.io/
8
9 ## Accounts
10
11 This is a fairly simply yet powerful framework, it stores all information into a
12 sqlite database and then propagates the modifications using dbus so all applications
13 using libaccounts will be aware of the modifications.
14
15 ### libaccounts-glib
16
17 The first thing to compile is libaccounts-glib, which is the code implementing
18 all the Read/Write/Notification of Accounts:
19
20 git clone https://gitlab.com/accounts-sso/libaccounts-glib libaccounts-glib
21 cd libaccounts-glib
22 meson build
23 ninja -C build && ninja -C build install
24
25 ### libaccounts-qt
26
27 This is the Qt bindings for libaccounts-glib, it uses qmake.
28
29 git clone https://gitlab.com/accounts-sso/libaccounts-qt libaccounts-qt
30 cd libaccounts-qt
31 qmake
32 make && make install
33
34 Note that at this very day libaccounts-qt qmake does **NOT** support compiling the
35 library outside the source directory, this means that the command qmake must be
36 executed within the root of libaccounts-qt and not for example in a build directory.
37
38 ##SSO
39
40 Single Sign On is the part of the framework responsible for storing and obtaining
41 credentials. It stores the credentials in a secure way (in case of KDE within
42 KWallet) and has a plugin system to do authentication in most common cases such
43 oauth/2 or simple user and password.
44
45 An interface can be plugged into SSO, at this moment we are using ubuntu's
46 implementation signon-ui but that will changes in the future.
47
48 ### signond
49
50 This includes a daemon that will be dbus activated and will offer a set of dbus api
51 to access to credentials and to authenticate to services (google/facebook oauth or
52 owncloud user/password). Within this same repo there is a Qt library that we'll use
53 in our applications to talk to the daemon.
54
55 git clone https://gitlab.com/accounts-sso/signond signond
56 qmake
57 make && make install
58
59 Note: Since signond is *dbus* activated be sure that the file
60 `com.google.code.AccountsSSO.SingleSignOn.service` is in a location where dbus
61 can find it (usually /usr/share/dbus-1/services)
62
63 ### Wallet support
64
65 In order for sigond to talk to KWallet we need a plugin for it, otherwise it will
66 store secrets (tokens and passwords) in plain text
67
68 git clone git://anongit.kde.org/signon-kwallet-extension.git
69 mkdir signon-kwallet-extension/build
70 cd signon-kwallet-extension/build
71 cmake ..
72 make && make install
73
74 ### oauth2 plugin
75
76 This plugin makes signond able to deal with oauth2 authentication
77
78 git clone https://gitlab.com/accounts-sso/signon-plugin-oauth2 signon-plugin-oauth2
79 mkdir signon-plugin-oauth2/build
80 cd signon-plugin-oauth2/build
81 qmake ..
82 make install
83
84 ### signon-ui
85
86 signon-ui provides the user interface for logging-into various accounts.
87
88 git clone https://gitlab.com/accounts-sso/signon-ui signon-ui
89 cd signon-ui
90 qmake
91 make install
92
93 ### kde providers
94
95 This are the providers and services that at this very moment we provide support for.
96 For example in Facebook we support Chat, Contacts Calendar... for what we need a
97 facebook.provider and chat/contacts/calendar.service files. This is basically a bunch
98 of icons and .xml files
99
100 git clone git://anongit.kde.org/kaccount-providers.git
101 mkdir kaccount-providers/build
102 cd kaccount-providers/build
103 cmake ..
104 make install