Timeline for Windows Service with authentication, some UI required
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 15, 2019 at 17:42 | history | edited | HoneyBadger | CC BY-SA 4.0 |
added 8 characters in body
|
| Jan 13, 2018 at 6:48 | vote | accept | HoneyBadger | ||
| Jan 12, 2018 at 13:01 | history | edited | HoneyBadger | CC BY-SA 3.0 |
added 39 characters in body
|
| Jan 12, 2018 at 12:31 | answer | added | Ewan | timeline score: 1 | |
| Jan 12, 2018 at 12:26 | comment | added | HoneyBadger | @BartvanIngenSchenau...Good point. The service will in all likelihood get it's own credentials. I wouldn't want to hardcode those credentials in the sourcecode though. The credentials would also give access to our SVN repositories, for example. Hence, I think it's better to have a user log in. (Additionally, I haven't been able to programmatically login. The steps involved are: 1. User logs in using username/password 2. User gets a PIN code, which is fed back to the application, 3. Application is authorised. Step 1 I haven't been able to do programmatically (yet).) | |
| Jan 12, 2018 at 11:30 | comment | added | Bart van Ingen Schenau | Why does your service need to login to the API with the personal account of a user?Can't the service authenticate itself with credentials that belong to the service? | |
| Jan 12, 2018 at 9:55 | review | First posts | |||
| Jan 12, 2018 at 13:17 | |||||
| Jan 12, 2018 at 9:53 | history | asked | HoneyBadger | CC BY-SA 3.0 |