idproject
int64 7.76k
28.8M
| issuekey
int64 675k
128M
| created
stringlengths 19
32
| title
stringlengths 4
226
| description
stringlengths 2
154k
⌀ | storypoints
float64 0
300
⌀ |
|---|---|---|---|---|---|
7,128,869 | 19,967,897 |
2019-04-11 13:48:12.761
|
Insight API endpoint /getDataSubjects returns incorrect content-type
|
* URL
`https://insight-api.test.voorbeeld-haarlem.nl/getDataSubjects`
* Response
```
{"dataSubjects":{"burgerservicenummer":{"label":"Burgerservicenummer"},"kenteken":{"label":"Kenteken"}}}
```
**Expected**
Header `Content-Type` with `application/json` as value
**Actual**
Header `Content-Type` with `'text/plain; charset=utf-8` as value
**Add tests!**
| 1 |
7,128,869 | 19,768,936 |
2019-04-05 13:07:17.436
|
Links in Navigation bar point to wrong environments
|
**As a** visitor of NLX.io
<br>**I want to** use the menu in relation to the environment that I'm in
<br>**so that** I won't get confused by the wrong links
---
Depends on move to Gatsby (#540)
**:white\_check\_mark: Acceptance criteria**
1. When you are on https://docs.test.nlx.io/ and click on "about" you should always go to right environment
1. Should also work for review envs
**:hammer\_and\_wrench: Proposed technical solution**
* Small Javascript using Environment Variables (env.json)
**:link: Reference links**
* [Existing script in Insight UI](https://gitlab.com/commonground/nlx/blob/9f0a69d05577be62e407724ffcb17549d5d86fff/insight-ui/docker/startup.sh) to expose environment variables from the Docker container to the browser's `window.env`
| 2 |
7,128,869 | 19,752,959 |
2019-04-04 21:50:47.958
|
Consistent licence information
|
**As a** PO
<br>**I want** it to be clear which licence is applicable to our code
<br>**so that** there can be no doubt about the license
**:white\_check\_mark: Acceptance criteria**
1. Add individual licence statements to all code files
1. Make sure there is a licence defined in the root of the repository + README
**:hammer\_and\_wrench: Proposed technical solution**
*
**:link: Reference links**
*
| 2 |
7,128,869 | 19,685,059 |
2019-04-03 11:36:45.350
|
PoC: Administrator dashboard
|
**As a** developer
<br>**I want to** have a PoC for the administrator dashboard
<br>**so that** we have a clear picture of what (and how) we want to build the dashboard
**:white\_check\_mark: Acceptance criteria**
1. PoC showing setting up an inway with a single command (docker run)
2. Provide documentation describing the setup
**:hammer\_and\_wrench: Proposed technical solution**
*
**:link: Reference links**
* #429
| 13 |
7,128,869 | 19,487,741 |
2019-03-27 10:55:02.178
|
Provide technical CHANGELOG
|
**As a** NLX user
<br>**I want to** see the changes between NLX versions
<br>**so that** I can foresee the upgrade path
**:white\_check\_mark: Acceptance criteria**
1. There should be a CHANGELOG available for NLX, automatically generated from commit logs
1. Instructions for devs, in contribution.md
1. Validated list of components and exact way to spell them (scopes)
1. Start with current version +1 (continue sequence)
**:hammer\_and\_wrench: Proposed technical solution**
* https://semantic-release.gitbook.io/semantic-release/
**:link: Reference links**
* https://gitlab.com/commonground/cg-design-system
* https://keepachangelog.com/en/1.0.0/
* TODO: setup gitlab token for semantic-release
| 3 |
7,128,869 | 19,487,053 |
2019-03-27 10:31:18.142
|
Make URLs in the context of NLX predictable
|
**As a** NLX user
<br>**I want to** have predictable URLs in the context of NLX
<br>**so that** a service can offer APIs that provide linked data
Currently URLs in NLX are structured as:
```
http://{outway}/{organization-name}/{service-name}
```
This structure makes URLs in NLX unpredictable as `{outway}` is different in every organization.
With this story we want to support request URLs in the following format:
```
http://{service-name}.{organization-name}.services.nlx.local
```
by adding functionality to the outway. This makes URLs in the context of NLX predictable.
**:desktop_computer: How to demonstrate**
1. Start an outway
1. Set `HTTP_PROXY` env variable to the address of the outway
1. Use curl to make a request to http://{service-name}.{organization-name}.services.nlx.local
1. The request should be received by {service-name} of {organization-name}
1. Use curl to make a request to {outwayaddress}/{origanization}/{service}
1. The request should be received by {service-name} of {organization-name}
**:white\_check\_mark: Acceptance criteria**
1. The outway forwards requests to hosts with the TLD `.services.nlx.local` to the specific service on NLX.
1. `HTTP_PROXY` is used
1. New feature is described in docs
**:hammer\_and\_wrench: Possible technical solutions**
**:question: Open questions**
1. Do we want requests on NLX to be explicit (`*.*.nlx.local`)? Or should we allow internet-routable hostnames te be fetched over NLX implicitly through a SRV record in the public DNS (`*.org.nl`) as well? ->Yes we should allow internet-routable hostnames te be fetched over NLX as a follow up story
1. Should we route non-NLX requests through the outway as well? Possible idea's:
- Yes, but with a log in the txlog
- Yes, but we should forward non-NLX requests to an organization proxy
**:warning: Possible problems**
1. Organization names with spaces and dots are not usable when we switch to a hostname, so we should introduce hostname-friendly slugs.
**:link: Reference links**
* PoC #508
* WIP https://gitlab.com/commonground/nlx/nlx/merge_requests/376
* WIP https://gitlab.com/commonground/nlx/draw-io/-/blob/master/concepts/OutwayProxySetup.drawio
**:microphone: Request for feedback**
* Joost (Kadaster)
* @sergei-maertens
**:hammer\_and\_wrench: Proposed sequence diagram**
| 8 |
7,128,869 | 19,310,031 |
2019-03-20 15:26:59.645
|
Update TTL for online services to 1 day
|
**As a**
<br>**I want to**
<br>**so that**
**:white\_check\_mark: Acceptance criteria**
1. Offline services are removed after 24 hours
**:hammer\_and\_wrench: Proposed technical solution**
*
**:link: Reference links**
*
| 1 |
7,128,869 | 19,308,961 |
2019-03-20 14:49:12.832
|
Add OAS specification for Outway Authorization
|
**As a**
<br>**I want to**
<br>**so that**
**:white\_check\_mark: Acceptance criteria**
1. OAS document API between outway and authz adapter/service
**:hammer\_and\_wrench: Proposed technical solution**
* Add spec file to repository
* Link redoc or similar in the readme/docs
**:link: Reference links**
*
| 3 |
7,128,869 | 19,308,937 |
2019-03-20 14:48:29.857
|
Add documentation for Outway Authorization
|
**As a**
<br>**I want to**
<br>**so that**
**:white\_check\_mark: Acceptance criteria**
1. Add document about outway autorisation to further reading
1. Questions by Amsterdam are addressed in the documentation
**:hammer\_and\_wrench: Proposed technical solution**
*
**:link: Reference links**
*
| 5 |
7,128,869 | 19,288,659 |
2019-03-20 12:34:24.827
|
Implement Outway Authorization based on PoC
|
**As a** nlx-user
<br>**I want to** configure my outway to use a authorization service
<br>**so that** calls going through my outway are authorized
**:white\_check\_mark: Acceptance criteria**
1. Require TLS connection between outway and autorisation server
1. Let authz _acknowledge_ headers, instead of adding them
**:hammer\_and\_wrench: Proposed technical solution**
* Based on Ronald PoC
| 5 |
7,128,869 | 19,087,038 |
2019-03-13 21:45:27.985
|
Add instructions to use NLX with Docker for Windows
|
**As a** Windows user
<br>**I want to** have instructions to get started
<br>**so that** I don't have to switch to Mac or Linux to use NLX
**:white\_check\_mark: Acceptance criteria**
1. The 'Get started' section should be compatible with Windows 10
**:hammer\_and\_wrench: Proposed technical solution**
* https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/
* https://www.vagrantup.com
**:link: Reference links**
* Documentatie van Berenschot: [Documentatie_050819.docx](/uploads/4138559d709720f7835eef34fa49b1d7/Documentatie_050819.docx)
| 5 |
7,128,869 | 18,806,368 |
2019-03-05 12:28:04.989
|
Add debug statements to inway registration
|
Discussed in standup, add debug statements to inway registration, which is problematic for some users.
| 1 |
7,128,869 | 18,709,382 |
2019-03-01 09:33:43.491
|
Add TLS between client and outway
|
**As an** nlx-user
<br>**I want to** secure traffic between my application and the outway
<br>**so that** nobody can snoop my data
**:white\_check\_mark: Acceptance criteria**
1. Outway can be configured with a self-signed certificate
1. Outway supports TLS connections from clients, TLS v1.2 and up
1. Outway requires the usage of TLS
**:hammer\_and\_wrench: Proposed technical solution**
*
**:link: Reference links**
*
| 5 |
7,128,869 | 18,649,015 |
2019-02-27 14:57:23.436
|
[PoC] outway proxy
|
**As a** NLX developer
<br>**I want to** know if the outway proxy design is feasible
<br>**so that** I can improve the design and work towards a new way of handling requests over NLX
**:white\_check\_mark: Acceptance criteria**
1. Outway handles traffic using HTTP_PROXY setup
**:hammer\_and\_wrench: Proposed technical solution**
*
**:link: Reference links**
*
| 8 |
7,128,869 | 18,643,323 |
2019-02-27 11:54:45.124
|
Implement Insight design
|
**As a** user
<br>**I want to** use a consistent and future proof ui
<br>**so that** I have a reliable user experience.
**:white\_check\_mark: Acceptance criteria**
1. Implement design (landing, scan, logs, wizard) scoped to design link
1. Create generic components when applicable (add to design system)
1. Design is not optimized for mobile but the content should accessible
1. Current dependencies should be removed (base.css, MaterialUI & jQuery) should be removed
1. Implement using `styled-components`
**:link: Reference links**
Design: https://sketch.cloud/s/wxR9w/p/insight
| 8 |
7,128,869 | 18,326,373 |
2019-02-18 14:39:05.827
|
Inway: use assert package in go tests
|
**As a** developer
<br>**I want to** use `"github.com/stretchr/testify/assert"` to do my assertions
<br>**so that** I conform myself to the go standard
**:white\_check\_mark: Acceptance criteria**
1.
**:hammer\_and\_wrench: Proposed technical solution**
*
**:link: Reference links**
*
| 2 |
7,128,869 | 18,321,596 |
2019-02-18 12:40:42.383
|
[PoC] Authentication service for the outway
|
**As a** NLX user
<br>**I want to** configure my own authentication service to be used by the outway
<br>**so that** requests made through my outway are authenticated.
**:white\_check\_mark: Acceptance criteria**
1. Authentication service definition in gRPC
1. Authentication service is configurable on the outway
1. When a authentication service is configured each request to the outway will be verified using the configured service.
1. Outway logs user-specific headers set by the authentication service.
1. Outway strips user-specific headers before sending it to the inway of a service that is not within the organization of the outway.
1. Reference implementation of the authentication service based on hardcoded users.
1. NO docs / NO unit tests
**:hammer\_and\_wrench: Proposed technical solution**
* Outway sends authentication request to the authentication service containing:
* Destination organization
* Destination service
* Request path
* The contents of `X-NLX-Authentication` header (arbitrary text)
* Transactionlog id (generated by the outway)
* Authentication service decides whether the request may continue, and optionally provides values that the outway can set onto the outgoing request for the fields:
* `X-NLX-Requester-User`
* `X-NLX-Requester-Claims`
**:link: Reference links**
* nlx/design/authentication-within-organizations.md
| 13 |
7,128,869 | 18,300,796 |
2019-02-17 18:22:50.068
|
Draw NLX in typical infrastructures of gov organisations
|
**As an** infrastructure manager
<br>**I want to** know how NLX fits in typical infra architectures
<br>**so that** I can decide to integrate NLX in my organisation
**:white\_check\_mark: Acceptance criteria**
1. At least three different, typical infrastructure overviews with NLX implemented
1. Created in Archimate
**:hammer\_and\_wrench: Proposed technical solution**
*
**:link: Reference links**
*
| 3 |
7,128,869 | 18,259,252 |
2019-02-15 08:43:25.068
|
Exclude TLS v1.2 support
|
**As a** Architect
<br>**I want to** use TLS version v1.3 and exclude v1.2
<br>**so that** NLX works faster, is more secure and complies with the advice of the Forum Standardisation (https://www.forumstandaardisatie.nl/sites/bfs/files/FS%20181010.3A%20Forumadvies%20TLS%201.3.pdf)
**:white\_check\_mark: Acceptance criteria**
1. All inter-nlx components : minimum TLS v1.3
1. `Client -> Outway` & `Inway -> API` : minimum TLS v1.2
1. Exclude unsafe cyphers for v1.2
**:hammer\_and\_wrench: Proposed technical solution**
* exclude TLS v1.2 support and heb exclude the following ciphers:
- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) ECDH x25519 (eq. 3072 bits RSA)
- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) ECDH x25519 (eq. 3072 bits RSA)
- TLS_RSA_WITH_AES_128_GCM_SHA256 (0x9c)
- TLS_RSA_WITH_AES_256_GCM_SHA384 (0x9d)
- TLS_RSA_WITH_AES_128_CBC_SHA (0x2f)
- TLS_RSA_WITH_AES_256_CBC_SHA (0x35)
- TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA (0xc012) ECDH x25519 (eq. 3072 bits RSA)
- TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa)
**:link: Reference links**
* https://www.forumstandaardisatie.nl/standaard/tls
* https://www.forumstandaardisatie.nl/sites/bfs/files/FS%20181010.3A%20Forumadvies%20TLS%201.3.pdf
**QUESTIONS:**
- can we update to 1.3 without causing failures in the current eco system?
*yes, see: https://gitlab.com/commonground/nlx/nlx/-/issues/492#note_363856136*
| 2 |
7,128,869 | 18,126,684 |
2019-02-11 09:37:29.373
|
Version numbers shown in FE applications
|
**As a** user
<br>**I want to** see which version is running when opening one of the NLX apps
<br>**so that** I don't work under the wrong assumption
**:white\_check\_mark: Acceptance criteria**
1. Version number & commit hash is visible for txlog-ui, directory-ui and insights-ui in javascript console (table).
1. Use https://directory.demo.nlx.io/version.json
| 2 |
7,128,869 | 18,066,788 |
2019-02-08 09:23:59.283
|
Inway: compare SELF_ADDRESS with certificate domain
|
**As a** NLX user
<br>**I want to** prevent an inway to start when a mismatch exists between self_adddress and certificate
<br>**So that** I cannot config an inway which will never be available
**:white\_check\_mark: Acceptance criteria**
1. Inway prints a error message when there is a mismatch between `SELF_ADDRESS` and certificate
1. the inway fails during start
**:hammer\_and\_wrench: Proposed technical solution**
*
**:link: Reference links**
*
| 2 |
7,128,869 | 18,007,218 |
2019-02-06 13:29:29.300
|
Version numbers shown in containers
|
**As a** user
<br>**I want to** see which version is running when starting a NLX container
<br>**so that** I don't work under the wrong assumption
**:white\_check\_mark: Acceptance criteria**
1. Version number & commit hash is available in every image (inway, outway, insight-api, tx-api, txlog-api, directory-inspection-api, directory-registration-api, directory-ui, insight-ui, txlog-ui)
1. Version number & commit hash is shown in terminal when starting one of the above containers
1. This information should be added for every commit
**:link: Reference links**
* Frontend part is described in #486
* Related to #460
| 3 |
7,128,869 | 17,963,124 |
2019-02-05 10:35:09.670
|
Api point url and api response in the API documentation are difficult to read (increase contrast)
|
**As a** API user
<br>**I want to** be able to easily read api point url and response example
<br>**So that** I can understand API requirements
**:white\_check\_mark: Acceptance criteria**
1. The api point url and the response are easy to read
**:hammer\_and\_wrench: Proposed technical solution**
- See if we can get the styling to work as default: http://rebilly.github.io/ReDoc/#operation/updatePetWithForm
- Could be that there is still custom styling overrides active.
- If above doesn't work, change text color to black
**:link: Reference links**
* https://directory.demo.nlx.io/documentation/Enable-U/DemoService#operation/callStockDilutionUsingGET
| 2 |
7,128,869 | 17,915,004 |
2019-02-03 10:31:33.024
|
Ensure high availability (HA) for all environments
|
**As a** dev, ops
<br>**I want to** have access to a highly available central services
<br>**So that** I can sleep at night
**:white\_check\_mark: Acceptance criteria**
1. Increase replica count in k8s deployment for all central services
**:hammer\_and\_wrench: Proposed technical solution**
* Use LBaaS feature of Fuga R2 (as mentioned by @GeertJohan in the comments)
**:link: Reference links**
*
| 2 |
7,128,869 | 17,886,001 |
2019-02-01 12:39:10.363
|
Document how to use the log level parameter for inway and outway
|
**As a** NLX user
<br>**I want to** know how I can set the log level of a inway and/or outway
<br>**So that** I can debug my inway/outway
**:white\_check\_mark: Acceptance criteria**
1. The LOG_LEVEL environment variable is described in the docs (startup guide)
1. Update:
* https://docs.nlx.io/try-nlx/management/getting-up-and-running
* https://docs.nlx.io/try-nlx/management/consume-an-api
* https://docs.nlx.io/try-nlx/management/provide-an-api
* https://docs.nlx.io/try-nlx/config-file/consume-an-api
* https://docs.nlx.io/try-nlx/config-file/provide-an-api
| 1 |
7,128,869 | 17,813,697 |
2019-01-30 15:09:11.935
|
Evaluate access rights for repo changes
|
**As PO**
<br>**I want to make sure access rights for all nlx repos are "least privilege"**
<br>**so that only intended people can alter our production namespace**
**:white\_check\_mark: Acceptance criteria**
1. Changes in infra on namespace / node level are reserved for ops specialists
2. Changes to core components are reserved for maintainers and owners
3. Proposal in slack
**:hammer\_and\_wrench: Proposed technical solution**
*
**:link: Reference links**
*
| 2 |
7,128,869 | 17,810,224 |
2019-01-30 13:16:50.182
|
Sort logs latest first
|
**:pencil2: Description**
**As a user of the Insight app**
<br>**I want to see the newest log entries first**
<br>**so that I don't have to click to the last page to see that what I just came for**
**:white\_check\_mark: Acceptance criteria**
1. Logs should be sorted descending by the `created` property
**:hammer\_and\_wrench: Proposed technical solution**
*
**:link: Reference links**
*
| 1 |
7,128,869 | 17,804,133 |
2019-01-30 09:57:18.858
|
Implement directory design
|
**As a** nlx user
<br>**I want** a future proof directory
<br>**So that** I will keep using it
**:white\_check\_mark: Acceptance criteria**
1. Implement [design](https://sketch.cloud/s/wxR9w)
1. Create generic components when applicable
1. Design is not optimized for mobile but the content should accessible
1. Current dependencies should be removed (base.css, MaterialUI & jQuery) should be removed
1. Implement using `styled-components`
**:link: Reference links**
* https://sketch.cloud/s/wxR9w
| 8 |
7,128,869 | 17,567,606 |
2019-01-22 14:47:36.251
|
Add inway version feedback to the health check for directory-monitor
|
Helpful to know which version of inway is running, this can be added to the health check exchange
| 2 |
7,128,869 | 17,481,315 |
2019-01-18 20:57:55.436
|
insight-api: add the ability to configure certificates and https
|
**:pencil2: Description**
**As a** nlx-user
**I want to** use https on the insight-api
**So that** my data is secure
| 2 |
7,128,869 | 17,481,062 |
2019-01-18 20:47:25.838
|
Make sure the Insight app unregisters old service workers automatically
|
Bugreport: Old service worker in insight app causes app to load with blank screen
- When loading the insight app (https://insight.demo.nlx.io/) in Chrome, I get a blank screen and a few errors.
- Inspection showed that there was an old service worker still active, somehow causing the app startup to fail.
- After manually unregistering the service worker, the app worked as expected.
Proposed solution: Make sure the Insight app unregisters old service workers automatically
| 1 |
7,128,869 | 17,465,656 |
2019-01-18 13:50:55.355
|
Cleanup offline services in directory after 14 days
|
**:pencil2: Description**
**As a** NLX user
**I want to** have an overview of active services on the directory ui
**So that** I know which services I can rely on
**:white\_check\_mark: Acceptance criteria**
1. Directory should clean up inways that are offline for 14 days
1. This period should be reflected in the docs
1. The 'cleanup threshold' should be configurable when starting the directory container
**:hammer\_and\_wrench: Proposed technical solution**
* Store the 'last online time' per service in the database
| 3 |
7,128,869 | 17,465,242 |
2019-01-18 13:32:42.332
|
Add contact details to service config
|
Add contact details to service configuration.
Perhaps two e-mail addresses would suffice:
* tech (for questions from NLX management, this one is not public)
* public (for questions from NLX end users to other end users, which is published in directory UI)
Can be optional, so non-breaking (for now).
Tasks:
* Create design
* Update database
* Update directory registration/inspection API
* Update inway
* Update documentation
* Implement design
**Design**
<br>https://sketch.cloud/s/wxR9w/p/directory
- Ignore the telephone number (depiction of possible extra contact info in the future).
- Ignore other design changes in directory, this will be applied in a different ticket.
| 1 |
7,128,869 | 17,400,630 |
2019-01-16 18:21:01.279
|
Fix font in svg used in docs
|
https://docs.test.nlx.io
On Safari/MacOS the text is shown in wrong font
| 1 |
7,128,869 | 17,387,151 |
2019-01-16 11:30:10.109
|
Move marketing site nlx.io from Github to Gitlab
|
**:pencil2: Description**
**As a** developer
**I want to** have all NLX related code available on GitLab
**So that** development is easier
**:white\_check\_mark: Acceptance criteria**
1. The CI / CD pipeline should be configured on GitLab
1. The commit history should not be preserved
1. Deployment should be available on `nlx.io`
1. Deployment is only for PROD. Other environments will be configured as part of another story.
**:hammer\_and\_wrench: Proposed technical solution**
*
**:link: Reference links**
* https://github.com/VNG-Realisatie/nlx.io
* https://gitlab.com/commonground
| 3 |
7,128,869 | 17,386,890 |
2019-01-16 11:20:51.923
|
Design a versioning policy
|
**As a** customer
<br>**I want** to know what the version policy of NLX is
<br>**so that** I know what measures to take for internal maintenance policy
**:white\_check\_mark: Acceptance criteria**
1. We have a page in our documentation that describes how we release and what we expect from system administrators.
1. We have internal documentation that describes how we handle breaking changes and our version skew policy.
**:link: Reference links**
- [X-Road](https://confluence.niis.org/display/XRDKB/Release+Notes) uses a simple semantic version system, also documented in more detail [here](https://github.com/nordic-institute/X-Road-development/blob/master/DEVELOPMENT_MODEL.md#34-publish). In Finland they recommend their production users to update within four weeks after the central server has been updated.
- [Chrome](https://www.chromium.org/getting-involved/dev-channel), has release channels
- [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine/docs/concepts/release-channels), has release channels
- [NodeJS releases](https://nodejs.org/en/about/releases/), uses semantic versioning with LTS
- [Ember.js releases](https://emberjs.com/releases/), uses semantic versioning with LTS
| 3 |
7,128,869 | 17,386,516 |
2019-01-16 11:10:23.806
|
Make Docs navigation structure clearer
|
- Improve styling so that subpages are more distinguished (indent).
| 1 |
7,128,869 | 17,385,941 |
2019-01-16 10:54:05.775
|
Add info logging to the inway
|
As a user who is configuring a inway I would like to see logging of the inway so I can debug issues which I may have during implementation.
Log:
* Certificates loaded.
* Calls to the directory.
* Service-config being loaded.
* Calls coming from a outway.
Acceptance criteria:
- More verbose logging of NLX components (status logs etc.)
- Logging is easily obtainable through for example `tail -f`
- The documentation describes how to view logs
| 2 |
7,128,869 | 17,385,932 |
2019-01-16 10:53:52.989
|
Add info logging to the outway
|
As a user who is configuring a outway I would like to see logging of the outway so I can debug issues which I may have during implementation.
Log:
* Certificates loaded
* Calls to the directory
* Calls made to the outway
Acceptance criteria:
- More verbose logging of NLX components (status logs etc.)
- Logging is easily obtainable through for example `tail -f`
- The documentation describes how to view logs
| 2 |
7,128,869 | 17,385,866 |
2019-01-16 10:51:29.162
|
Add Getting started guide to docs.nlx.io
|
Getting Started contains the following steps:
- Preparing
- Certificates
- Using a service
- Start an outway
- Providing a service
- Start an inway
- Transactionlogs
Create example based on Docker Compose.
Reuse docker compose.yml made by @RonaldKoster
As a Getting Started (walkthrough) with parts, like: https://docs.docker.com/get-started/
Every part needs a verification step (check if your action went well).
| 8 |
7,128,869 | 17,385,780 |
2019-01-16 10:49:11.567
|
Write docs on how to setup transaction logs
|
- https://docs.nlx.io/transactionlogs/ is filled with documentation
- Add links to transaction log setup docs on start an inway and start an outway pages (--env DISABLE_LOGDB=1)
| 5 |
7,128,869 | 17,385,413 |
2019-01-16 10:37:16.493
|
Update documentation based on user feedback
|
Check where this information needs to be added in the docs and
update the documentation to make it clear that:
- An outway is needed to contact an inway.
- How to mitigate problems with containers that are tagged with :latest.
- How to check if your inway/outway is running.
- The directory exists and that the services offered by an inway can be published in the directory.
- The directory can be used to check if a service is online.
- That localhost on a docker container does not resolve to the hostmachine.
| 3 |
7,128,869 | 17,253,373 |
2019-01-10 23:48:32.268
|
Add link to public demo on front page
|
Add a link to demo.nlx.io somewhere on the nlx.io front page, possibly drawing some attention to it
| 1 |
7,128,869 | 17,206,145 |
2019-01-09 14:04:13.227
|
Upgrade IRMA-api-server
|
As communicated by IRMA, in their step to moving to a new IRMA api server implementation, they are releasing an update to the current one. We need to stay up to date. See the communication:
1. Update the IRMA api server and release to production/demo BEFORE 31 jan 2019
2. Report to Sietse that we have updated
```
Dear everyone,
I am mailing to everyone I know that runs or is otherwise interested in the irma_api_server, https://github.com/privacybydesign/irma_api_server. This email is about the future of the irma_api_server, its upcoming replacement in Go, and also about future emails like these.
Let me start with something to do:
*Please update your irma_api_server to the latest version as soon as possible, but at least before January 31.*
Otherwise, your irma_api_server will be incompatible with an upcoming version of the IRMA app, that we will release at that time. The reason is explained below.
1) The eventual deprecation and replacement of the irma_api_server
The irma_api_server has been very useful and important for the IRMA ecosystem, but it has its drawbacks; it is not very flexible, or easy to configure, or easy to experiment with. Ever since we switched to the Go programming language for the IRMA app, we have been planning to eventually completely switch to Go. Therefore, we have been working on a new IRMA server in Go, that will eventually replace and deprecate the irma_api_server. This new server has been designed to be:
- Easy to deploy and use in a multitude of environments and use cases,
- Simple to configure and easy to experiment with,
- More efficient and scalable across server farms,
- more easy to automatically test using CI/CD.
Additionally, the new irmaserver improves legacy issues, fixes shortcomings, and improves efficiency in the protocol that it uses when issuing or verifying attributes from IRMA apps. It will be released as a library for use in backend server applications, as well as a standalone server like the irma_api_server. This new server (simply called "irmaserver") will be mostly compatible with the current irma_api_server. Not entirely, but when the new irmaserver is released we will simultaneously release an update of irma_js that will abstract away the differences for you as much as possible.
2) End of life of the irma_api_server
In the migration to the new irmaserver there needs to be a compatibility mechanism that ensures that all IRMA apps works with both the new irmaserver and the old irma_api_server. In order not to pollute the new server with legacy code, we have decided to implement this compatibility mechanism in the irma_api_server, with an update adding compatibility with the upcoming version of the IRMA app, which will be released on February 1. After that, irma_api_servers that have not yet been updated will become incompatible with the latest version of the IRMA app. This is why it is necessary that all irma_api_servers are updated. *Once your server is updated, please let me know.*
After the update introducing compatibility with both the old and the new upcoming versions of the IRMA app, the irma_api_server will no longer be actively developed, apart from bug fixes and security updates. The new irmaserver will be released soon after that.
3) Future mails like these
IRMA is, by design, a decentral system: anyone can run IRMA servers without involvement of us (the Foundation). This is an important and distinguishing feature contributing to IRMA's trustworthiness, but it also means we (the Foundation) have no way to automatically update all IRMA infrastructure. Although we of course try to prevent making breaking changes, sometimes this is unavoidable. We have to prevent that this leads to a fractured IRMA ecosystem with incompatible apps and servers, which would lead to bad user experience and hurt adoption.
As an alternative update channel, we will henceforth sometimes send emails like this one. The release of the upcoming irmaserver will be announced like this too. If you do *not* want to receive these emails please let me know, but in order to keep the IRMA experience for users as stable and reliable as possible, *we strongly recommend anyone running an irma_api_server, or the new irmaserver after it has been released, to stay on this list*. If you know anyone who you think should receive these emails as well, please let me know.
Kind regards,
Sietse Ringers.
```
| 1 |
7,128,869 | 17,064,595 |
2019-01-03 19:21:02.010
|
Clarify current situation of environments and targets audiences (with visual)
|
- Create clear description of current target audiences, environments
- Markdown file available on gitlab
- Relevant visuals available
- Clear name & versioning convention incl url
- Show how this relates to build/deploy pipelines
- Plan how to communicate to target audiences
NLX devs have their own flow with several public environments, next to the public environments ment for demo, pre prod and production.
It helps to clarify which is which, including some visual that shows flow for audiences.
Rough sketch (won't be accurate in current form, but exactly that is the problem - needs clarification)
| 5 |
7,128,869 | 16,795,049 |
2018-12-19 16:22:52.620
|
Update gitlab runner go version to 1.11.4
|
We want to keep using golang:1-alpine in our docker images because we don't want miss any security updates. The latest version of go currently is 1.11.4. and this version produces different hashes as previous versions when running go mod tidy. Because of this our gitlab runner will not pass go.mod.tidy test.
We need to update our git lab runner to use go version 1.11.4 so we can keep using golang:1-alpine in our docker images
| 1 |
7,128,869 | 16,658,034 |
2018-12-14 10:43:09.705
|
Create an business overview of 'how to start with NLX'
|
**As a** Business representative
<br>**I want to** have a business overview of NLX
<br>**So that** I can asses what I need to implement NLX and what the business benefits are after implementing NLX.
<br>*NLX documentation so far is clear for (most) developers. What i see is that almost every municipality that is interested in connecting with NLX is searching for a functional (business) overview of 'how to start with NLX?'.
In most municipalities they have to start a project and need to find a budget before they can start (...). So the business needs to understand it first, before some technical people will make a start. For Business people/management the current documentation is not sufficient.*
**:white\_check\_mark: Acceptance criteria**
**The Business overview is available on https://docs.nlx.io/ and makes clear:**
1. What kind of people do i need (what kind of knowledge is required)?
2. What environment(s) do i need?
3. What kind of tools/functionaly do i need in my municipality to connect with NLX?
4. What will be the investment?
5. How much time is estimated for a first connection, a PoC?
6. Which connections are easy tot start with?
7. Acceptance of the business overview by @dennisdewit!
8. What the business benefits are after implementing NLX!
**:hammer\_and\_wrench: Proposed technical solution**
* business overview document in Markdown
* overview in public available Archimate model
**:link: Reference links**
* https://docs.nlx.io/
*
| 8 |
7,128,869 | 16,586,569 |
2018-12-11 22:36:04.775
|
Bump dependency due to CVE
|
Dependency with high severity [CVE-2018-16469](https://nvd.nist.gov/vuln/detail/CVE-2018-16469)
Package merge
Vulnerable versions: < 1.2.1
Patched version: 1.2.1
https://gitlab.com/commonground/nlx/blob/master/txlog-ui/package-lock.json#L3980
https://gitlab.com/commonground/nlx/blob/master/txlog-ui/package-lock.json#L7022
| 1 |
7,128,869 | 16,329,263 |
2018-12-04 23:55:30.161
|
Front page nlx.io text layout breaks
|
See attached screenshot
MacOS 10.14, Safari 12.0
| 1 |
7,128,869 | 16,286,663 |
2018-12-03 12:45:44.835
|
Insight-ui RDW backend demo api returns 500
|
Possible solutions:
1. In depth configuration Check @GeertJohan [timebox 3 uur]
2. Get rid of navigation item & long term solution by IRMA team [1 point]
After selecting rdw from the list and scanning QRCode the api call to RDW getproof api point returns 500.
api url (jwt from this sample will expire)
https://irma-api.demo.voorbeeld-rdw.nl/api/v2/verification/jZpQZz9AmUqMSeB5GTZDZIpBfp4iMscKtgNvVTyAo6nW/getproof
response received: {
"error": "EXCEPTION",
"status": 500,
"description": "Encountered unexpected problem",
"message": "io.jsonwebtoken.SignatureException: Unable to calculate signature using RSA PrivateKey. Could not sign data"
}
| 1 |
7,128,869 | 73,524,801 |
2020-10-28 14:29:44.777
|
Add all available service data from API to NLX management directory
|
Show all date we have in the directory detail drawer.
- Button to documentation
- Button to specification
- Support addresses
- Flip the status and API type below the title. Status first, then API type (because there is not always an API type to be shown)
- Note: the inline error alert is positioned above the buttons.
**Acceptatie criteria**
1. All data from API result is placed on detail pane as specified in attached design
1. Icon on docs en specs button is smaller than normal
| 2 |
7,128,869 | 73,524,613 |
2020-10-28 14:27:26.746
|
Styled dropdown in settings
|
We use a select component in the settings, but it is without (dark mode) styling. See:
We have a styled react-select component in the appstore, but it is not in de design system yet. <br>
**Acceptance criteria**
1. Make component available (from appstore) in design system
1. White dropdown on settings page replaced with the new component
| 3 |
7,128,869 | 73,524,516 |
2020-10-28 14:26:00.170
|
Empty states for collapsibles
|
The empty states within collapsibles are in regular texts right now. This should be in `<small>` text, to make it visually clear that it is not content.<br> Also, the text has a hover and active state, but it is not clickable. It should not have any interaction states.
**Acceptance criteria**
1. All empty states styled as empty states
Current situation:<br>
Design:<br>
| 1 |
7,128,869 | 73,524,426 |
2020-10-28 14:24:26.244
|
Move settings menu item below
|
The settings menu item should be secundair, shown at the bottom.<br>
Note: there is a spacing of `1rem` between the bottom of the navigation and the lowest menu item.
| 1 |
7,128,869 | 73,463,444 |
2020-10-27 15:08:51.331
|
Make sure UI represents actual state after actions
|
**As a** _user_
<br>**I want** the UI to automatically update after an action
<br>**so** I don't have to manually refresh or open the service detail to see the actual state
Actions:
- request access
- approve access request
- reject access request
- retry access request after fail
- revoke access
--
Out of scope: updating list of orgs with access after granting access
**:desktop_computer: How to demonstrate / e2e test(s):**
1.
**:white\_check\_mark: Acceptance criteria**
1. After actions listed above, show new state in frontend
**:link: Reference links**
1.
**Implementation**
- API's should give new state as result on the call
| 3 |
7,128,869 | 72,977,264 |
2020-10-19 18:30:47.371
|
Combine inspection and registration API into directory API
|
**As a** maintainer
<br>**I want** to combine inspection and registration API into one new directory API
<br>**so** that the whole setup becomes more easy to understand and less work to maintain
**:white\_check\_mark: Acceptance criteria**
1. Inspection and registration API combined into new directory API
1. This should not be breaking
1. Add deprecation warning to the directory registration api URL and directory inspection api URL flags both will be replace by a single directory API url
1. Reuse a fixed IP of the registration/inspection API for the combined directory API so that the existing firewalls rules still work.
1. Update the IP reference information on docs.nlx.io
**:link: Reference links**
1.
| 13 |
7,128,869 | 72,972,891 |
2020-10-19 16:39:13.521
|
Proxy browser traffic to Mngt API through Mngt UI
|
**As a** sysadmin
<br>**I want** to easily setup NLX Management
<br>**so** that I cannot make any mistakes and save some time
**:white\_check\_mark: Acceptance criteria**
1. Connection from browser (via LB) to Management API is no longer needed / possible
1. Remove nginx config
1. Setup go project
1. Use go static file server
1. Setup reverse proxy fpr /api /oidc
1. html/css/js are embeded in the executable. Serve actual files when developing
1. build go binary in docker file
1. update helm chart
**:tools: Technical implementation**
- Management UI changes from Nginx to Go server with html/css/js
- Requests from browser to Management API goes through Management UI
IST:
SOLL:
**:link: Reference links**
1.
| 5 |
7,128,869 | 72,960,224 |
2020-10-19 13:07:55.312
|
Migration to Postgres DB from ETCD
|
**As a** developer
<br>**I want** to use a database type which is more suited for NLX management
<br>**so** that efficiency is increased
Currently we use an ETCD database. As the feature list of NLX management becomes more complete we are realsing that ETCD, which is a key value database, might not be the right choice. Objects like services, access requests, access grants are tightly related to eachother and storing these objects in a key value database is making less and less sense.
Replacing the key value database with a relational database seems like the right choice.
With a relational database we can:
* easily retrieve related objects adn therefore greatly simplify the management API codebase
* improve data integrity
**:desktop_computer: How to demonstrate / e2e test(s):**
1.
**:white\_check\_mark: Acceptance criteria**
1. Support for SQL type databases (mysql, msql, postgres), avoid database specific functionality.
1. ETCD database is replaced by postgress
1. Management API executable can do it's own migrations
1. Support for TLS on database connection
1. User GORM as ORM (https://gorm.io/)
1. Support SQLite for development
Implementation
1. Use migrate (https://github.com/golang-migrate) for migrations
1. Migration is embeded in the management API
Technical implementation
1. Start management API with `serve` command to serve API
1. Start management API with `migrate` command to do migrations
Tasks:
1. [x] Create datamodel
1. [x] Create migrations
1. [x] Update helm charts / deployments
1. [x] Update documentation
1. [x] Implement running migrations using the binary
1. [x] Package migration files into the binary
1. [x] Implement GORM in management-api
1. [x] Solve access request locking with new database
1. [x] Check which GRPC calls require DB transactions
1. [ ] Use SQLite for testing
1. [ ] Clean demo environment (volume claims, tokens, secrets)
**:link: Reference links**
1.
| 20 |
7,128,869 | 72,850,332 |
2020-10-16 17:56:33.674
|
Shine: add logout icon to menu
|
Add a small icon to the 'logout' menu option, as shown here:
https://www.sketch.com/s/89b1e1ac-ec61-482a-bc78-8d1b811bf210/a/exY0lq
| 1 |
7,128,869 | 72,710,166 |
2020-10-14 12:15:00.961
|
Show different counter when there are 0 access request
|
When there are 0 access request, the regular counter can be shown in the collapsible. <br>
Only show the notification bubble counter when there is 1 access request or more.<br>
See designs attached.
| 1 |
7,128,869 | 72,708,387 |
2020-10-14 11:51:38.796
|
Display warning when no organisation inway is selected
|
**As an** provider of services
<br>**I want** a very annoying and clear warning when I do not have an inway selected to receive incoming access requests
<br>**so** that requesting organisations can submit their access requests
**:desktop_computer: How to demonstrate / e2e test(s):**
1.
**:white\_check\_mark: Acceptance criteria**
1. On starting the application: when an organisation offers at least one service and does not have an organisation inway configured, a system warning should be shown on every page.
1. Check if the banner should still be visible: when updating the organization inway, when update/add/remove a service.
Note: we will need to update this logic when we implement delegation
**:link: Reference links**
1.
**:unicorn: Design proposal**
- Non dismissible banner on top (as part of the header?)
- Visible on all pages
- Stays until an organization inway is chosen
- The link goes to the settings page
- NLX management specific component
<br><br>Old design:<br>[/uploads/2c34ae5b9a4e00c0d3fe7149a4e0b898/Banner.png]()
<br><br>New design:<br>
| 3 |
7,128,869 | 72,704,486 |
2020-10-14 10:56:24.415
|
After revoked access grant, new request should be possible
|
**As a** user of a requesting organisation
<br>**I want** to be able to request access again after my access is revoked
<br>**so** that I can retry after I've fixed the reason over which my access was revoked
Currently, when org B revokes access to a service, org A cannot request access again.
This is even worse since the UI behaves as if you can request access, although the flow won't work.
**:white\_check\_mark: Acceptance criteria**
1. After access to a service is revoked, a new request for access to that same service can be made
**Implementation**
1. Access request state has to be in sync on both sides, this requires a poll mechanism that polls until resolved
1. After access granted, this grant needs to be exchanged and stored on requesting side
**:link: Reference links**
1.
### Insights and TODO's
A `service` has `latestAccessRequest` and `latestAccessProof`. When access has been rejected, the access proof will get a `revokedAt` property.
This would make it possible for us to show a "Request access" button to create a new access request.
However, if a new access request is created, the `latestAccessProof` is still there. We need it to be there to display the right data, but it makes it difficult to show the state of the **new** access request.
We cannot compare the `revokedAt` date with the `createdAt` date of the new access request, because these dates are created by different clocks (systems).
- [ ] Therefore (and maybe other reasons) we need to set a `accessRequestId` prop on the `accessProof` object.
- [ ] Then we can update the frontend (`directoryServiceAccessState`) to show the correct things on screen.
| 5 |
7,128,869 | 72,634,647 |
2020-10-13 10:43:13.363
|
Set the new 'permissions' policy header
|
**As a** sysadmin
<br>**I want** the NLX frontend to have complete security headers
<br>**so** that our hygiene is tip top
Set the 'permissions' header in all our frontends.
More important for public frontends than the Management UI
We do not allow anything. All permissions disallowed.
**:white\_check\_mark: Acceptance criteria**
1. Headers set
**:link: Reference links**
1. https://scotthelme.co.uk/goodbye-feature-policy-and-hello-permissions-policy/
| 2 |
7,128,869 | 72,256,934 |
2020-10-06 13:12:48.186
|
Toaster "in" animation broken in nlx
|
*Expected behaviour*
toaster should slide in from the right
*Actual behaviour*
toaster just appears
**:clipboard: Steps to reproduce**
1. add/edit a service and submit
1. toaster should become visible as described in "expected behaviour"
**:mag: Details**
Not an issue in DS itself
---
| 2 |
7,128,869 | 71,938,119 |
2020-09-30 11:40:32.657
|
Enable insight UI configuration when using NLX Management
|
**As a** beheerder
<br>**I want** to be able to use the insight UI when using NLX Management
<br>**so**
This is part of #1024. Before working on this, discuss with FE, BE & designer how we will solve this.
**:desktop_computer: How to demonstrate / e2e test(s):**
1.
**:white\_check\_mark: Acceptance criteria**
* The NLX Management should be sufficient to setup an environment to give the 'official NLX demo' (parkeervergunningen app), without having to use `nlxctl`
**Settings to be added to the NLX Management settings page**
- InsightAPIURL
- IrmaAPIURL
**:link: Reference links**
1.
| 3 |
7,128,869 | 71,861,043 |
2020-09-29 09:40:24.979
|
Retry a failed access request
|
**As a** nlx management user
<br>**I want** to be able to retry a failed access request
<br>**so** that I do not get stuck in a dead lock
**:desktop_computer: How to demonstrate / e2e test(s):**
1.
**:white\_check\_mark: Acceptance criteria**
1. Pressing "Probeer opnieuw" will retry the access request
1. After pressing "Probeer opnieuw" the error Alert component disappears and the error message in the request access block changes to a spinner
1. On error while retrying, show toaster with error. Reset UI to initial state.
1. State should automatically update in UI of requesting organisation (without refresh)
**:link: Reference links**
1.
| 3 |
7,128,869 | 71,860,353 |
2020-09-29 09:27:33.720
|
Enable testing the grant access flow for the Review Apps
|
**As a** developer
<br>**I want** the be able to manually test the access grant flow
<br>**so** that we deliver a flawless product
**:desktop_computer: How to demonstrate / e2e test(s):**
1.
**:white\_check\_mark: Acceptance criteria**
1. Creating an access request can be tested manually
1. Accepting an access request can be tested manually
1. Revoking an access grant can be tested manually
1. Out of scope: automate test flow using E2E-tests
**Notes**
1. Add NLX Management for the organization Haarlem
1. Keep config for BRP 'as is' to make sure the Parkeervergunning app still works
1. NLX Management for Haarlem should be accessible from the Review Overview page
**:link: Reference links**
1.
| 3 |
7,128,869 | 71,858,302 |
2020-09-29 08:57:55.233
|
Revoke access grant
|
**As a** nlx management user
<br>**I want** to able to revoke granted access
<br>**so** that organizations no longer have access to my services
revoke:<br>
**:desktop_computer: How to demonstrate / e2e test(s):**
1.
**:white\_check\_mark: Acceptance criteria**
> Above design is shown in sub drawer, which is similar to access request.
1. Revoking an access grant optimistically updates the UI state
1. On error while saving, show toaster with error. Reset UI to initial state.
1. Show confirmation dialog before revoking access
1. Organization no longer has access
1. State should automatically update in UI of requesting organisation (without refresh)
| 3 |
7,128,869 | 71,858,136 |
2020-09-29 08:55:08.501
|
View organizations with access
|
**As a** nlx management user
<br>**I want** view organizations with access grants to my service
<br>**so** I known which organizations have access
**:desktop_computer: How to demonstrate / e2e test(s):**
1.
**:white\_check\_mark: Acceptance criteria**
1. Access grants are displayed in the service detail view
1. Displaying difference between public keys of a organization is out of scope
**:link: Reference links**
1.
| 3 |
7,128,869 | 71,791,132 |
2020-09-28 10:19:06.164
|
Add audit logging to NLX Management
|
**As a** compliancy officer
<br>**I want** to see all user-initiated actions in the audit trail
<br>**so** that I can make informed statements about compliancy and
**As a** system admin
<br>**I want** to see all user-initiated actions in the audit trail
<br>**so** that I see what actions led to the current situation
Add the following events to the audit trail:
- User logs in/out
- Login attempts
- New service CRUD
- Incoming/Outgoing access requests - all actions
- Access grants created/revoked
- Access proof created/revoked
- Settings page - all changes
**:white\_check\_mark: Acceptance criteria**
1. All actions which can be done in NLX management should be logged
1. Every action that is logged should contain structured data:
- the action (type)
- date/time
- organization
- device used (~~ip-address~~[**](#ip-address)/browser/terminal/client)
- user
- a field for meta data
1. If logging fails no actions should be executed. After the action there is no second log to confirm the action has succeeded
1. Audit trail is visible on new 'audit log' page in NLX Management (only list items, without filters/pagination)
> This should be all the icons. Could one of you check if it is complete? -Peter
**Out of scope**
- NLX Management role granted/revoked to new user
- Relevant part of audit trail on each specific detail page
- Audit logs are 'immutable' (e.g. if a row is deleted, this breaks a hash chain) For now I think we should keep this in mind but not implement it yet, as it comes with requirement for UX/Design. But we should
**:desktop_computer: How to demonstrate / e2e test(s):**
1. When one of the actions (described above) is performed, add to audit log
1. go to audit log page
1. see my actions
---
> **<a name="ip-address"></a> ip-address CAN be seen as too privacy-sensitive. So we are not including it for now
>
> 
| 5 |
7,128,869 | 71,621,281 |
2020-09-24 11:02:26.106
|
Show state of access request in requesting organisation
|
Progress:
- [x] Polling mechanism (api to api) !1921
- [x] Expose ~~`lastestAccessGrant`~~ `latestAccessProof` !1935
- [x] Show latest access request states !1931
- [x] Show latest access grant states !1961
---
**As a** user that requests access
<br>**I want** to see the status of my request
<br>**so** that I know if I have access yet
After requesting access:
- keep polling of state of access request changes
- once request accepted, fetch the grant
After grant is fetched and stored:
- change status in UI to 'ACCEPTED'
Note: the UI does NOT do polling. See accepted state by closing and opening the drawer.
When access revoked (unknown yet for requesting org):
- keep polling for state change
- revoke local access grant
- change UI to 'Toegang ingetrokken' (detail drawer and on service row in directory)
**implementation**
Access grant:
1. api will poll every 5 seconds to inway of org B to retrieve access request status
1. API will poll for access grant once status changes to 'approved'
1. When refreshing the UI, 'Je hebt toegang' will be visible once grant is available in requesting organisation
Revoke:
1. Access request state has to be in sync on both sides, this requires a poll mechanism that polls until resolved
1. After access granted, this grant needs to be exchanged and stored on requesting side
**:white\_check\_mark: Acceptance criteria**
1. For all below, UI = service row on directory page and service detail pane
1. When access request is clicked and 'ack' is received, UI shows 'Toegang gevraagd'
1. When grant is received, 'Je hebt toegang' is shown.
1. When access is revoked, UI in requesting org shows 'Toegang ingetrokken'
1. After access to a service is revoked, a new request for access to that same service can be made
Out of scope: showing what happens when 'rejected'
Out of scope: polling in the UI
**:link: Reference links**
1.
| 8 |
7,128,869 | 71,536,025 |
2020-09-22 21:37:42.326
|
Deprecation of treating TLS CommonName as host name
|
The certificates that we produce with our unsafe CA, based on the instructions [here](https://docs.nlx.io/try-nlx/retrieve-a-demo-certificate), are not compatible with the deployment on demo enviroment. This results in all services that use those certificates being offline.
A temporary fix was applied, by temporarily re-enabling the old behavior by adding the value x509ignoreCN=0 to the GODEBUG environment variable and deploying the relevant demo environment components.
A permanent fix is required.
Urgent:
- [x] We will automatically add the common name to the subject alternative name in the CA cert portal
- [ ] We will create new demo pki*
- [ ] We will include the intermediate cert in the request cert response
- [ ] We will inform the demo users about the breaking change
- [ ] We will document that a certificate must be newer than and why AND something about the intermediate certificate
Next steps:
- [ ] If possible/feasable, add a test that catches this error when deploying
*We will create a new pki because we do not sign demo the same way as prod and will change demo so it resembles prod
*Expected behaviour*
* Online services are shown online in directory of demo environment
*Actual behaviour*
* Online services are shown offline in directory of demo environment
**:clipboard: Steps to reproduce**
Note: due to temporary fix no longer visible in demo environment. Reproducing is not recommended.
1. Deploy an environment which trusts our Unsafe CA root, without the x509ignoreCN=0 env variable
1. Use certs generated according to the instructions on https://docs.nlx.io/try-nlx/retrieve-a-demo-certificate
1. See all services fail in directory
**:beetle: Cause**
* In Go 1.15 implementation of X5.09 certs, treatment of CommonName field as hostname is deprecated
https://golang.org/doc/go1.15#commonname
* The certificates that we instruct new users of NLX to generate, do no longer work correctly with our release that uses Go 1.15
**:mag: Details**
Example logs due to this bug:
`{"level":"INFO","time":"2020-09-21T15:37:31.326Z","caller":"inway/inway.go:250","message":"directory registration successful","version":"v0.87.1","inway-organization-name":"utrecht"}
2020-09-21 15:37:36.057073 I | http: TLS handshake error from 192.168.73.0:45365: remote error: tls: bad certificate
2020-09-21 15:37:36.075355 I | http: TLS handshake error from 192.168.73.0:4044: remote error: tls: bad certificate
2020-09-21 15:37:36.075481 I | http: TLS handshake error from 192.168.73.0:63007: remote error: tls: bad certificate
2020-09-21 15:37:36.082503 I | http: TLS handshake error from 192.168.73.0:11627: remote error: tls: bad certificate
2020-09-21 15:37:36.082776 I | http: TLS handshake error from 192.168.73.0:45641: remote error: tls: bad certificate
2020-09-21 15:37:36.090492 I | http: TLS handshake error from 192.168.73.0:55237: remote error: tls: bad certificate
2020-09-21 15:37:36.090559 I | http: TLS handshake error from 192.168.73.0:24471: remote error: tls: bad certificate`
---
| 5 |
7,128,869 | 71,251,441 |
2020-09-16 13:50:36.853
|
Remove Whitelist / Open access radio buttons from UI
|
**As a** beheerder
<br>**I want** to use the whitelist only when not using NLX management
<br>**so** both type of users can still restrict access to their services and NO whitelist option in NLX management
**:desktop_computer: How to demonstrate / e2e test(s):**
1.
**:white\_check\_mark: Acceptance criteria**
1. all code which is used to store / add / etc entries to the whitelist must be removed
**:link: Reference links**
1.
| 2 |
7,128,869 | 71,249,705 |
2020-09-16 13:16:17.400
|
Show number of access requests on services overview
|
**As a** provider of services
<br>**I want** to see which of my services have open access requests (and how many)
<br>**so** that I know where my action is required
**:white\_check\_mark: Acceptance criteria**
1. Counter is shown on services overview on each row with open access requests
1. Visual Design is implemented
**Implementation**
1. BE: Add number of incoming access requests to service object (in list view)
1. FE: make sure the "counter" updates when fetching service detail
**:link: Reference links**
1.
| 3 |
7,128,869 | 71,115,434 |
2020-09-14 13:53:42.144
|
Add installation guide for NLX management to docs for testing purposes
|
**As a** system operator
<br>**I want** to known how to install NLX management
<br>**so** that I can play around with it
This is part of #1024.
Before starting with this, discuss with @ehotting and Ingebrid if our proposed solution is ok.
**:desktop_computer: How to demonstrate / e2e test(s):**
1. Go to docs.nlx.io
1. Follow steps in the NLX Management installation guide available on docs.nlx.io
1. End up with a working NLX Management setup
**:white\_check\_mark: Acceptance criteria**
1. Next to 'Try NLX', add the section 'Try NLX Management'
1. Add warning to the 'Try NLX' section that we're working on 'Try NLX Management' and the `config.toml` configuration will be deprecated in the future
1. Add warning to the 'Try NLX Management' section that this is a WIP.
**Notes**
1. Installation guide is aimed at a system running Docker
1. Installation steps available for:
- ETCD
- Dex
- Management API
- Management UI
1. Use Docker compose to setup local setup
1. Use environment variable to configure OIDC `.well-known-config-path`
**:link: Reference links**
1. Previous effort: https://nl-x.slack.com/archives/CU78R12LQ/p1601468678172700
| 8 |
7,128,869 | 70,963,133 |
2020-09-10 07:28:25.157
|
Reject access request
|
Implement the view for approving and rejecting access requests, and revoking when already accepted
Choice:
> Note: also see state flow model in [Epic](https://gitlab.com/groups/commonground/nlx/-/epics/12).
> Note 2: this component can be accessed from [service detail](#1004) or [dashboard](#998).
**:white\_check\_mark: Acceptance criteria**
1. Add endpoint to reject access
1. Rejecting an access request optimistically updates the UI state
1. On error while saving, show toaster with error. Reset UI to initial state.
TODO: @petervermeulen can you think of another icon to reject? The cross looks like deleting or throwing something away.
**:link: Reference links**
1.
| 2 |
7,128,869 | 70,963,083 |
2020-09-10 07:27:00.142
|
Accept incoming access requests and authorize requests based on access requests
|
**As a** provider of a service
<br>**I want** accept access requests
<br>**so** that the other organization can use my service
**:white\_check\_mark: Acceptance criteria**
1. My service detail pane should list open access requests
1. The accept request should display the requesting organization name
1. I can accept the access request by clicking accept and confirm through a dialog box
1. The result of the action is displayed in a toaster
1. After accepting the request should disapear from the service detail pane
1. After accepting the requesting organization has access
1. "Organizaties met toegang" is out of scope
**:link: Reference links**
1.
| 13 |
7,128,869 | 70,627,225 |
2020-09-02 11:02:30.378
|
FE: Access requests visible on dashboard
|
**As a** [beheerder]
<br>**I want** to see an overview of access requests on the dashboard
<br>**so** I can always see the requests regardless of the existence of the service
:warning: We don't have endpoints to collect all outgoing/incoming access requests. Only by servicename. So this story is not purely FE.
**:desktop_computer: How to demonstrate / e2e test(s):**
1. login to nlx management
1. dashboard is shown with a section displaying access requests
1. I can view incoming or outgoing access requests
1. I can click "view more" if there are more access requests, these will open in a drawer
1. click on a request, it will show details in a drawer
- this drawer will overlap the list view if it was open
1. I see a placeholder for the access request detail view
**:white\_check\_mark: Acceptance criteria**
1. Work with mock data on the frontend
1. view (max 5) access requests grouped by service
1. I can open the list view in drawer to see more/all access requests
1. able to open the request; To see details in drawer
- if clicking on a request in the section: directly show details
- if clicking on a request in the "list drawer": show "drawer-in-drawer"
1. the detail pages show placeholders
**:link: Reference links**
1.
| 5 |
7,128,869 | 58,923,768 |
2020-07-15 09:45:13.343
|
Remove IE11 support
|
**As** many stakeholders
<br>**I want** to drop IE11 support
<br>**so** I can spend more resources to actually implementing features
**:desktop_computer: How to demonstrate / e2e test(s):**
1. Visit the app with IE11 and see a redirect to a page explaining it doesn't support IE11
(Not sure if we can automate this single test as an e2e-test)
**:white\_check\_mark: Acceptance criteria**
1. A good feature to test for (check if browser supports it) is [Proxy](https://caniuse.com/#feat=proxy)
If the browser does not support it, we should redirect to a page explaining we don't support outdated browsers
(Note: Proxy is also a feature used by [mobx v5](https://mobx.js.org/README.html#browser-support))
1. Revisit the currently used polyfills, remove any that don't apply anymore to save bundle size
1. Whatever page the user opens (via bookmark of just the login page), the redirect should work.
1. List supported browsers.
**layout proposal**
https://www.sketch.com/s/89b1e1ac-ec61-482a-bc78-8d1b811bf210/a/R0Wn8j<br><br>
**Tech sollution**
> Agreed upon by Niels & Jorn
- Create the above design in `public/index.html`, which is the base template for the app
- Inside the `<div id="root">`
- This way if there is an error you will see the "browser support" page
- To prevent this page flashing before the app loads, we can use CSS Transitions to only show the page after X seconds
- On slow connections you may still see the browser support page before the app loads
- If there is NO error, react will simply overwrite the `#root` div and you won't see the page
This is a nice universal approach we can also use in our other projects
| 2 |
7,128,869 | 54,143,748 |
2020-07-09 07:19:39.815
|
Access Request reaches the other organization
|
**As a** user of a service
<br>**I want** to send acces requests to the organization that provides the service
<br>**so** that the other organization knows that I want access
**Tasks**
- [x] Create an AccessRequest when the user clicks "Request access"
- [x] Send a created AccessRequest from org A -> org B
- [x] Being able to set the primary inway for management requests
- [x] Implement a management-api proxy on the inway for org B
- [x] Set organization inway address in postgres after selecting the default ingress
- [x] Receive and store AccessRequest from org A in org B
- [x] Implement proper unique constraint on out/in-coming access requests
**Steps**
- access request can have state=created
- ar sending succeeds
- communication between organizations runs through a proxy on the Inway of the receiving organizations
- ar state changes to received
- ar received is known in the management api
**:desktop_computer: How to demonstrate / e2e test(s):**
1.
**:white\_check\_mark: Acceptance criteria**
1. The public key finger print should be stored with the access request on both sides
1. There can only be one access request open per service/public key finger print
1. An access request can be send and received with a response about the state
**:link: Reference links**
1.
list: https://www.sketch.com/s/89b1e1ac-ec61-482a-bc78-8d1b811bf210/a/zPE5ka
detail: https://www.sketch.com/s/89b1e1ac-ec61-482a-bc78-8d1b811bf210/a/Jlbwz9
| 13 |
7,128,869 | 54,143,477 |
2020-07-09 07:14:56.771
|
One service can only be exposed by one Inway
|
**As a** NLX beheerder
<br>**I want** have a one on one relation between service and inway
<br>**so** the service is only exposed by one inway
**:desktop_computer: How to demonstrate / e2e test(s):**
1.
**:white\_check\_mark: Acceptance criteria**
**BE**
1. NLX mgt UI - can only choose one inway. No choice will show the current not available message
1. mgt API - model must be changed so it a service can only contain one inway
1. Directory - model must be changed to one service on one inway relationship
1. Directory - must reject the registration when a inway tries to register the same service with a different self address
Dirctory: There will be a breaking change
- We prefer to do this immediately
- Another option is to make a backward-compatible version in between
This depends on a chat with users of "prod" & "pre-prod"
Same goes for inways
**FE**
NLX Management:
This currently expects an array for connected inways in services
This should change to a single entry
Directory UI:
Also work with a single entry instead of array for displaying status
**UI changes**<br>
[https://www.sketch.com/s/89b1e1ac-ec61-482a-bc78-8d1b811bf210/v/eaaEyz/a/Jlbwz9/r/RMomoj](https://www.sketch.com/s/89b1e1ac-ec61-482a-bc78-8d1b811bf210/v/eaaEyz/a/Jlbwz9/r/RMomoj)
**:link: Reference links**
1.
| 5 |
7,128,869 | 35,437,745 |
2020-06-04 14:22:43.723
|
Semantic release for Helm charts
|
The Helm chart have two versions: the version of the chart and the version of the application. The application version reflects the version of NLX.
- When we release a new version of NLX the application version should be updated.
- When the application version changes, the chart version should increase.
Right now it is a manual step to change the version numbers of the charts. A of writing we didn't release a new version of NLX and the charts didn't need a version change.
We can solve this in two ways:
- Give the Helm charts their own version numbering<br>
`Chart 0.1.0 -> 0.2.0 -> 0.3.0`<br>
`Application 0.86.0 -> 0.87.0 -> 0.87.1`
- Use the NLX version also for the chart<br>
`Chart 0.86.0 -> 0.87.0 -> 0.87.1`<br>
`Application 0.86.0 -> 0.87.0 -> 0.87.1`
Either way the semantic release tool needs to change the version number.
| 2 |
7,128,869 | 35,417,864 |
2020-06-04 07:52:36.228
|
Directory in NLX management shows all services including your own
|
**As a** beheerder
<br>**I want** to see all services in the directory in NLX management
<br>**so** I have a complete overview there and do not have to go to the public website
Possible iterations:
1. one list containing all
1. one list with filtering or
two lists, one for all others and one for mine
1. later maybe also one list for all services I'm connected to via my outway?
**:desktop_computer: How to demonstrate / e2e test(s):**
1.
**:white\_check\_mark: Acceptance criteria**
1.
**:link: Reference links**
1.
| 2 |
7,128,869 | 35,368,816 |
2020-06-03 08:20:15.706
|
Implement toaster in NLX
|
Implement our freshly made toaster component in our projects, on the following locations:
## Todo
1. After creating a new service, you'll be redirected to that newly created service (the drawer), with a toaster.
1. After editing a service, you'll be redirected to that service, with a toaster.
1. After removing a service, you'll see the service overview page and a toaster (currently a localised Alert).
1. Reuse the same message/content from the message.
| 2 |
7,128,869 | 35,368,039 |
2020-06-03 08:13:23.345
|
Management: keep item in list visibly selected
|
**As a** user
<br>**I want** the selected item in list to be visibly selected
<br>**so** I have an easy reference between the item in detail drawer and the list of items
For example on Services page, when service in list is clicked it is selected and Drawer opens with details.
The item in list gets focus state with visual indication. But it loses focus when clicking somewhere else.
**:desktop_computer: How to demonstrate / e2e test(s):**
1. Go to services page
1. Click a service (drawer with details opens, focus is set to Drawer (default function of normal drawer))
1. Service in list is visibly selected by different background color
1. Pressing tab after clicking will focus first element in the Drawer
1. Clicking on an element in the detail drawer will keep the service visibly selected
1. Clicking another service in the list will make that one visibly selected
1. Focus will be reset to the Drawer (so pressing tab will once again select the first element in drawer)
**:white\_check\_mark: Acceptance criteria**
- Selected service item has coloured background (similar to `selected` state of dropdown in attached design)
- On click focus will reset to drawer
- When closing the drawer (pressing ESC or clicking X) will set **unset selected state**, but **set focus** on item
- Should work like this on all pages (eg: ServicesPage, InwaysPage)
**:tools: Tech**
- hover, active and selected states should be managed by `Table` component in DS
- Capturing focus should be default functionality of Drawer, even when background is not used (update `Drawer` in DS if necessary)
- ServicesPage (and others, like inways) will need to maintain a state property to know what the selected item is
**:paintbrush: Design**
Design tokens:<br>
*Light theme*
```
$color-background-dropdown-hover rgba(0, 0, 0, 0.1)
$color-background-dropdown-active rgba(0, 0, 0, 0.3)
$color-background-dropdown-selected rgba(0, 0, 0, 0.2)
```
*Dark theme*
```
$color-background-dropdown-hover rgba(255, 255, 255, 0.1)
$color-background-dropdown-active rgba(255, 255, 255, 0.3)
$color-background-dropdown-selected rgba(255, 255, 255, 0.2)
```
| 5 |
7,128,869 | 35,062,044 |
2020-05-27 12:04:17.111
|
Add inside info for admin when service has no inway
|
**As a** admin
<br>**I want** to be informed on several levels about the availability of my service
<br>**so** I easily see I need to give some TLC to a service
**:desktop_computer: How to demonstrate / e2e test(s):**
1. do the steps mentioned in the acceptance criteria and check if the message is displayed on three places: the add/edit form, the details drawer and the service list
**:white\_check\_mark: Acceptance criteria**
1. when you add or edit a service and you do not connect it to a inway (or remove the connection), then the message should be displayed (ALLREADY DONE)
1. Same situation as above: no inway is connected to a service: then you will see in the details drawer of the service the same message which is shown in the form
1. Same situation as above: no inway is connected to a service: then you will see in the service list the title of the message which is shown in the form and in the detail drawer
**:proposed solution**
- if inway count is 0 and boolean internal = False, then show on both appearances the standard message
- title of message should be: Geen inway gekoppeld
| 2 |
7,128,869 | 34,970,015 |
2020-05-25 09:50:15.558
|
Listen to 127.0.0.1 by default
|
## Problem
All our components that accept incoming requests (start listeners), like an inway and outway, listen by default to the `0.0.0.0` address. That means it will bound to all network interfaces. When you deploy an outway (or other component) on a server that is directly connected to the internet and no firewall is configured, it will expose the outway to the public internet. This might be a security risk.
## Proposal
Change the default value for all the 'listen' options in all components from `0.0.0.0:<port>` to `127.0.0.1:<port>`.
| 1 |
7,128,869 | 34,539,656 |
2020-05-14 08:25:07.863
|
Adopt new rules section in gitlab ci yaml
|
**As a** developer
<br>**I want** to use the current pipeline syntax for rules
<br>**so** my pipelines will run
In GitLab 13.0 the `only`/`except` syntax to specify when a job should be executed is changed to `rules`. In our case the `container_scanning` jobs overrides a gitlab template that has migrated to `rules`, while we specify `only`/`except`. See this [failed pipeline](https://gitlab.com/commonground/nlx/nlx/pipelines/145888217). This needs to be fixed asap. After that all jobs need to be updated to prevent future issues.
**:white\_check\_mark: Acceptance criteria**
1. no conflicting use of `rules` and `only`/`except` in jobs
1. all jobs use `rules`
**:link: Reference links**
1. https://about.gitlab.com/releases/2020/05/06/gitlab-com-13-0-breaking-changes/
| 2 |
7,128,869 | 34,432,607 |
2020-05-12 07:45:01.544
|
Link inway(s) to a service
|
**As an** [beheerder]
<br>**I want** to link one or multiple inways to a service
<br>**so** my service can be found and used by other organizations
**:desktop_computer: How to demonstrate / e2e test(s):**
1. Add a service
1. Fill in all details
1. select one or multiple inways
1. store the service
1. see that the service is added to the service list
1. see in the public directory that the service is available in the list
1. see in NLX management that the service is NOT visible since its your own service
**:white\_check\_mark: Acceptance criteria**
1. Add this functionality to the add/edit service form (see designs attached)
1. Works the same by editing a service, but linked inways are prefilled.
1. when no inways are available, then show message simular to the message on the inway page. The selection box and + link are hidden
1. When no inways are linked, and the option "publish in directory" is chosen, show an alert notification (see design below)
1. Update the order of the form fields (see design below)
**:link: Reference links**
1.
**Designs:**<br>
| 5 |
7,128,869 | 34,305,729 |
2020-05-08 09:31:35.371
|
Outway: use separate certificate for https endpoint
|
## Problem
The outway has two (internal) endpoints: http and https. Currently the https endpoint serves the (PKIO) organization certificate to the client. The problem with this is that the organization certificate should contain the internal domain name on which the outway is reachable. Besides this certificate is used for authenticating the outway on the NLX network.
## Proposal
Use separate certificate for the https endpoint. This should be explicit be configured, no fallback to the organization certificate. If it is desired to use the same certificate then this needs to be configured twice.
## Focus
This issue has a focus on the changes of the connection between the client and the outway. other issue's should address other points of the to-be situation for the outway
### Acceptance criteria / technical
* Add certificate bundle (certificate, private key, ca certificate) options to `nlx-outway`
* Validate as usual
* Use certificate bundle to start the https server
* Start HTTPs server only when certificate bundle is provided, including CA certificate
* CA certificate is required
### References
* Options: https://gitlab.com/commonground/nlx/nlx/-/blob/master/outway/cmd/nlx-outway/main.go#L24
* HTTPs server: https://gitlab.com/commonground/nlx/nlx/-/blob/master/outway/listen.go#L58-63
### Changes for the to-be situation
1. use the .local address https://en.wikipedia.org/wiki/.local
2. relocate the state of the Outway to the NLX Management component
3. add local certificates and keypairs
4. remove the "DISABLE_LOGDB" flagg and define the NLX_LOG_ADDRESS
-- when the adress is empty the logging should be disabled and the http headers should
include a warning stating that Logging is disabled in the outway
5. The client must inform the outway whitch organisation and service to adress. basically their are three options:
5.1 the client should add 2 headers that includes {organization-name}/{service-name}/ OR
5.2 the client should include the {organization-name}/{service-name} in the path OR
5.2 the client should include {organization-name}/{service-name} in the hostname
### Considerations:
if the response to the client includes a NLX domain consiting of https://nlx.{provider}.nl/
the response should be altered to replace :
-- https://nlx.{provider}.nl/{path} with
-- https://{consumer}.local/{organization-name}/{service-name}/{path}
hence making it possible to referens to a NLX resource in the response
The linked data issue should also be resolved for the outway to work as a proxy
hence making it possible to referens to a NLX resource in the response
the linked data issue should also be resolved for the outway to work as a proxy
https://gitlab.com/commonground/nlx/nlx/-/issues/316
https://gitlab.com/commonground/nlx/nlx/-/issues/530
https://gitlab.com/commonground/nlx/nlx/-/merge_requests/1337
| 2 |
7,128,869 | 33,312,838 |
2020-04-15 10:16:29.014
|
Outways page
|
**As a** administrator
<br>**I want** to have an overview of all the outways
<br>**so** that I can copy its Public Key PEM
**:desktop_computer: How to demonstrate**
1. Navigate to in/outway
**:white\_check\_mark: Acceptance criteria**
1. Rename menu item 'inways' to 'in/outway'
1. Display type toggle (all/inway/outway)
1. Implement detail pane
1. Enable copying the Public Key PEM from the detail pane
1. Do not implement search
1. Do not implement sorting
1. Outway should register itself to the management API
1. Outway should not start when management API url is missing
**Questions**
- Currently outways are not using the config API so the system does not know which outways are available?
**:link: Reference links**
1. In/Outways overview page: https://www.sketch.com/s/89b1e1ac-ec61-482a-bc78-8d1b811bf210/a/nPV5g0
1. Outway detail pane: https://www.sketch.com/s/89b1e1ac-ec61-482a-bc78-8d1b811bf210/a/Yxr5Lm
1. Add Public Key PEM field to the certificate info: https://www.sketch.com/s/89b1e1ac-ec61-482a-bc78-8d1b811bf210/a/1pzP3n
| 13 |
7,128,869 | 33,276,983 |
2020-04-14 15:29:11.951
|
Design System - Input component
|
Created separate story for extracting the input components into the Common Ground Design System.
**:white\_check\_mark: Acceptance criteria**
1. Input fields (text, radio & checkbox)
1. TextInput, RadioInput & CheckboxInput (helper components which include the label, input and validation message)
1. Documentation
1. Apply updates in Appstore & NLX Dashboard (the DON team should be informed about this).
| 5 |
7,128,869 | 33,264,588 |
2020-04-14 12:35:24.230
|
Implement toaster component
|
**As an** user
<br>**I want** clear feedback on my actions
<br>**so** that there is no doubt if my action was successful or not.
**:desktop_computer: How to demonstrate / e2e test(s):**
1.
**:white\_check\_mark: Acceptance criteria**
1. A component to give feedback on actions. Often called "toaster" or "alert notification". Which appears in the upper right corner.
1. Styling is the same as the inline alerts, with an added shadow and close icon.
1. There are 4 flavours, the same types as the inline alerts. (info, success, warning, error)
1. Animation specs are in the image attached.
**:link: Reference links**
1.
<br><br>
SVG close icon:<br>
`<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" width="24" height="24">
<polygon id="Path" points="0 0 24 24"></polygon>
<polygon id="Path" fill-rule="nonzero" points="12 10.8216667 16.125 6.69666667 17.3033333 7.875 13.1783333 12 17.3033333 16.125 16.125 17.3033333 12 13.1783333 7.875 17.3033333 6.69666667 16.125 10.8216667 12 6.69666667 7.875 7.875 6.69666667"></polygon>
</svg>`
| 2 |
7,128,869 | 32,728,142 |
2020-04-01 11:31:12.167
|
NLX Management: show organization name
|
**As a** _NLX Management user_
<br>**I want** _to see the organization name_
<br>**so** _that I know for which organization I perform actions_
**:desktop_computer: How to demonstrate / e2e test(s):**
1. just login and show
**:white\_check\_mark: Acceptance criteria**
1. Organization name comes from the (PKIO) certificate
On login page:
1. Show the organization name also on the login page and show that name fully
On other pages:
1. Only show organization name in normal font weight
1. Show ellipsis (...) when the name is longer then 20rem
1. Hover on the name, shows the complete name
**Proposed tech solution:**
* create new endpoint for fetching environment vars
**:link: Reference links**
1. 
1. The login page based on https://www.sketch.com/s/89b1e1ac-ec61-482a-bc78-8d1b811bf210/a/7L27xY
The rest of that design will be implemented in https://gitlab.com/commonground/nlx/nlx/-/issues/929
| 3 |
7,128,869 | 32,626,805 |
2020-03-30 11:15:24.075
|
Merge management-api and config-api
|
> One management-api to rule them all - Hugo
We would like to join the management-api and config-api so there is only one component with the responsibility to hold state within one organization. The new name is: **management-api**
Acceptance criteria:
- The config-api and management-api are combined in one component
- The inway uses the management-api for polling configuration
Technical design:
- The management-api listens on both 8080 (HTTP with session authentication) and 8443 (HTTPS mTLS)
| 5 |
7,128,869 | 32,122,681 |
2020-03-18 09:16:07.540
|
Management: change multi-language approach
|
Dutch will be the default language. However, because of international aspirations, the software (i18n keys and routing) should be English.
- [x] Change public facing URLs to English
- [x] Change translation strings to English
- [x] Add English and Dutch translation files. The English ones will initially be the same as the key strings.
- [x] Add some documentation about how to internationalization as developers
| 2 |
7,128,869 | 32,092,418 |
2020-03-17 15:08:48.894
|
Management: edit a service
|
**As a** administrator
<br>**I want** to edit a service
<br>**so** I can alter the configuration when needed
**:desktop_computer: How to demonstrate**
1. Select an existing service and change it settings
1. View service details to confirm new settings
**:white\_check\_mark: Acceptance criteria**
1. I am able to change the settings of a service
1. The service name is immutable
1. Show confirmation message when successful
1. Show error message on failure
**:link: Reference links**
1.https://sketch.cloud/s/eDOWa/a/3YxOja
| 3 |
7,128,869 | 32,091,213 |
2020-03-17 15:03:16.828
|
Management: remove a service
|
**As a** adminstrator
<br>**I want** remove a service
<br>**so** that services that are no longer provided to the NLX network
**:desktop_computer: How to demonstrate**
1. Create a service
1. Delete it
1. Navigate to service overview and confirm service is deleted
**:white\_check\_mark: Acceptance criteria**
1. Show confirmation dialog before deleting (native browser confirm)
1. Show confirmation when successful
1. Show error message on failure
**:link: Reference links**
1.https://sketch.cloud/s/eDOWa/a/3Yjyyj
| 2 |
7,128,869 | 32,091,104 |
2020-03-17 15:00:44.264
|
Management: service details
|
**As a** administrator
<br>**I want** to view the details of my services
<br>**so** that I know how a service is configured
**:desktop_computer: How to demonstrate**
1. Select a service from the services overview and display the details
**:white\_check\_mark: Acceptance criteria**
1. Implement design with available fields in the API
1. Extract drawer component into DS
1. Implement drawer into other consuming projects (DON & Appstore)
**:link: Reference links**
1. https://sketch.cloud/s/eDOWa/a/3Yjyyj
| 5 |
7,128,869 | 32,090,384 |
2020-03-17 14:48:01.543
|
Management: add a new service
|
**As a** administrator
<br>**I want** to add a new service
<br>**so** that I can offer services to the NLX network
**:desktop_computer: How to demonstrate**
1. Create a new service
1. Open the services overview
1. Find your new service
**:white\_check\_mark: Acceptance criteria**
1. Implement form as designed with the fields that are available in the API
1. For now we do not implement the field Inways -> follow up story
1. Show a confirmation message when the service has been created
1. Show error message when it fails
1. Navigate to service overview after successful creation
1. Extract input component into DS
1. Implement input into other consuming projects (DON & Appstore)
**:link: Reference links**
1. https://sketch.cloud/s/eDOWa/a/3YxOja
| 8 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.