Timeline for Is it secure to use SQL for storing authentication codes?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 24, 2016 at 17:35 | comment | added | Out of Band | I think your gut feeling tricks you. It takes time to understand how OAuth flows work and which one to use, but you only have to invest that time once, and writing the actual code to do authentication using Open ID really isn't much more complicated than doing an http redirect, sending one or two server-side https requests and verifying that some values you get sent are what you expect them to be. It's much simpler than you'd think. | |
| Oct 24, 2016 at 17:25 | comment | added | Twijn | Still seems more simple to just do it yourself. May be slightly less secure but again, security is not 100% needed. It's a private website, the security sits there only "just in case" I'll look into Let's Encrypt but I'm not sure if the host supports it. | |
| Oct 24, 2016 at 15:54 | comment | added | symcbean | +1 for openid, but changing the sessionid on each request creates a lot of complexity which will break in unexpected ways (arguably an interesting approach for a surrogate authentication token for use in Ajax requests though). | |
| Oct 24, 2016 at 15:07 | history | edited | Out of Band | CC BY-SA 3.0 |
added 279 characters in body
|
| Oct 24, 2016 at 14:55 | history | edited | Out of Band | CC BY-SA 3.0 |
added 230 characters in body
|
| Oct 24, 2016 at 14:42 | history | edited | Out of Band | CC BY-SA 3.0 |
added 216 characters in body
|
| Oct 24, 2016 at 14:35 | history | edited | Out of Band | CC BY-SA 3.0 |
added 695 characters in body
|
| Oct 24, 2016 at 14:28 | history | answered | Out of Band | CC BY-SA 3.0 |