Updated docs to reflect that chirpstack has been updated (#15)

Author: MadsSvejstrup

source/external-interface-design/external-interface-design.rst

@@ -130,7 +130,7 @@ and Chirpstack is out of scope of this project.
 
 |image6|
 
-The Chirpstack is comprised of the following 5 modules.
+The Chirpstack is comprised of the following 4 modules.
 
 1. `Appplication
    Server <https://www.chirpstack.io/application-server/use/fuota/>`__
@@ -139,11 +139,7 @@ The Chirpstack is comprised of the following 5 modules.
 
 3. `Gateway bridge <https://www.chirpstack.io/gateway-bridge/>`__
 
-4. `Geolocation
-   server <https://www.chirpstack.io/geolocation-server/>`__ (only for
-   locating edge devices)
-
-5. A postgresql database
+4. A postgresql database
 
 Data synchronization
 ~~~~~~~~~~~~~~~~~~~~

source/maintenance-guide/maintenance-guide.rst

@@ -95,7 +95,7 @@ Starting dependencies for development
 
    .. code-block:: bash
 
-      docker-compose up chirpstack-network-server postgresql chirpstack-gateway-bridge chirpstack-geolocation-server chirpstack-application-server os2iot-outbound-mosquitto mosquitto redis os2iot-inbound-mosquitto os2iot-kafka os2iot-postgresql os2iot-zookeeper
+      docker-compose up chirpstack-network-server postgresql chirpstack-gateway-bridge chirpstack-application-server os2iot-outbound-mosquitto mosquitto redis os2iot-inbound-mosquitto os2iot-kafka os2iot-postgresql os2iot-zookeeper
 
 3. To quit: In your terminal you can press Ctrl + C twice. This will safely shut down docker.
 

source/testing/testing.rst

@@ -25,7 +25,7 @@ Running the tests
 
     a. Start the dependencies using docker-compose from te OS2IoT-docker folder: 
 
-        i. :code:`docker-compose up --force-recreate --build -d chirpstack-network-server postgresql chirpstack-gateway-bridge chirpstack-geolocation-server chirpstack-application-server os2iot-outbound-mosquitto mosquitto redis os2iot-inbound-mosquitto os2iot-kafka os2iot-postgresql os2iot-zookeeper`
+        i. :code:`docker-compose up --force-recreate --build -d chirpstack-network-server postgresql chirpstack-gateway-bridge chirpstack-application-server os2iot-outbound-mosquitto mosquitto redis os2iot-inbound-mosquitto os2iot-kafka os2iot-postgresql os2iot-zookeeper`
 
 2. Install dependencies to run test from the OS2IoT-backend folder:
 

source/users-notes/users-notes.rst

@@ -25,41 +25,12 @@ How to change chirpstacks admin password
 Step-by-step:
 ############
 
-1. Create a user (e.g. [email protected]) in Chirpstack with the wanted password.
-2. Change the password_hash for ’admin’ in the postgres-database:
-    a. SSH into the server
-    b. docker exec -it os2iot-docker_postgresql_1 sh
-    c. psql -U chirpstack_as
-    d. update public.user set password_hash = (select password_hash from public.user where email = '[email protected]') where id=1;
-    e. Now the user has been updated
-3. Delete the user created in step 1
+1. Log in to the ChirpStack Application Server web interface using the default credentials
+2. Change the password of the admin user under: 'All users' -> 'admin' -> 'Change Password'
 
+In previous versions of ChirpStack Application Server it wasn't possible to change the admin user password through the UI, but since v.3.13.0 this as worked as expected.
 
-
-Background information: 
-######################
-
-
-In order for OS2iot to function, there must be an admin user in chirpstack named admin. This is because Chirpstacks API requires an JWT including  ’username’. You can read about JWT here: https://jwt.io/ and decode:  
-’ eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJjaGlycHN0YWNrLWFwcGxpY2F0aW9uLXNlcnZlciIsImV4cCI6MTYxODkyMTQ1NiwiaWQiOjEsImlzcyI6ImNoaXJwc3RhY2stYXBwbGljYXRpb24tc2VydmVyIiwibmJmIjoxNjE4ODM1MDU2LCJzdWIiOiJ1c2VyIiwidXNlcm5hbWUiOiJhZG1pbiJ9.H1ildZ6dj3_G-BkI9EPW6QJk_3QowpLUY4lL4vCcvX0’ 
-
-to 
-
-’ {
-  "aud": "chirpstack-application-server",
-  "exp": 1618921456,
-  "id": 1,
-  "iss": "chirpstack-application-server",
-  "nbf": 1618835056,
-  "sub": "user",
-  "username": "admin"
-}’ 
-
-That is, if the username is changed the JWT will not work anymore.
-
-Chirpstack requires that all its users has an e-mail, when they are created or changed (Including change of password). Nevertheless, when the application is created the first time / the database is created this is not a requirement. This is why you will not be able to change the password using Chirpstacks UI. 
-
-It is possible to change the requirement that the user must be named admin here:
+Alternatively the Admin user can removed and replaced by another user entirely. This requires changing the user name that OS2iot-backend uses:
 https://github.com/OS2iot/OS2IoT-backend/blob/master/src/services/chirpstack/jwt-token.ts#L17