Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
As I don't have any significant experience with internationally-standard information security literature, I would like to ask here if some international information security organization took the i...
#6: Post edited
As I don't have any significant experience with standard/international information security literature, I would like to ask here if some international information a security organization took the initiative to standardize the terms "authentication" in general and _authentication modules_ in particular as to well define what elements should such a module include.- What makes a software module an "authentication" module?
- I'd guess:
* Receive an email as input- * Receive a password as input
- * Possibly; receive a username as input
- * Possibly; receive an encryption private key as input
- * Possibly; receive a "two factor authentication data"
- * Possibly; receive a Captcha input
- As I don't have any significant experience with internationally-standard information security literature, I would like to ask here if some international information security organization took the initiative to standardize the terms "authentication" in general and _authentication modules_ in particular as to well define what elements should such a module include in minimum.
- What makes a software module an "authentication" module?
- I'd guess:
- * Receive a password as input
- * Possibly; receive an email as input
- * Possibly; receive a username as input
- * Possibly; receive an encryption private key as input
- * Possibly; receive a "two factor authentication data"
- * Possibly; receive a Captcha input
#5: Post edited
As I don't have any significant experience with standard/international information security literature, I would like to ask here if some international information a security organization took the initiative to standardize the term "authentication" in general and _authentication modules_ in particular as to well define what elements should such a module include.What makes a software module an "authentication" module? I'd guess:- * Receive an email as input
- * Receive a password as input
- * Possibly; receive a username as input
- * Possibly; receive an encryption private key as input
- * Possibly; receive a "two factor authentication data"
- * Possibly; receive a Captcha input
- As I don't have any significant experience with standard/international information security literature, I would like to ask here if some international information a security organization took the initiative to standardize the terms "authentication" in general and _authentication modules_ in particular as to well define what elements should such a module include.
- What makes a software module an "authentication" module?
- I'd guess:
- * Receive an email as input
- * Receive a password as input
- * Possibly; receive a username as input
- * Possibly; receive an encryption private key as input
- * Possibly; receive a "two factor authentication data"
- * Possibly; receive a Captcha input
#3: Post edited
What makes a software module an "authentication" module?As I don't have any significant experience with standard/international information security literature, I would like to ask here if some international information a security organization took the initiative to standardize "authentication" and authentication modules as to well define what should such module do?I would guess:- * Receive an email as input
- * Receive a password as input
- * Possibly; receive a username as input
- * Possibly; receive an encryption private key as input
- * Possibly; receive a "two factor authentication data"
- * Possibly; receive a Captcha input
- As I don't have any significant experience with standard/international information security literature, I would like to ask here if some international information a security organization took the initiative to standardize the term "authentication" in general and _authentication modules_ in particular as to well define what elements should such a module include.
- What makes a software module an "authentication" module? I'd guess:
- * Receive an email as input
- * Receive a password as input
- * Possibly; receive a username as input
- * Possibly; receive an encryption private key as input
- * Possibly; receive a "two factor authentication data"
- * Possibly; receive a Captcha input
#2: Post edited
Is there a standard meaning for the term "authentication"?
- What makes a software module an "authentication" module?
Is there a standard meaning for the term "authentication" (in the context of software development)?Was some international information a security organization took the imitative to standardize that term so to well-define what does authentication means? If so, what should an "authentication module" in a source code actually do?- I would guess:
- * Receive an email as input
- * Receive a password as input
- * Possibly; receive a username as input
- * Possibly; receive an encryption private key as input
- * Possibly; receive a "two factor authentication data"
- * Possibly; receive a Captcha input
- What makes a software module an "authentication" module?
- As I don't have any significant experience with standard/international information security literature, I would like to ask here if some international information a security organization took the initiative to standardize "authentication" and authentication modules as to well define what should such module do?
- I would guess:
- * Receive an email as input
- * Receive a password as input
- * Possibly; receive a username as input
- * Possibly; receive an encryption private key as input
- * Possibly; receive a "two factor authentication data"
- * Possibly; receive a Captcha input
#1: Initial revision
Is there a standard meaning for the term "authentication"?
Is there a standard meaning for the term "authentication" (in the context of software development)? Was some international information a security organization took the imitative to standardize that term so to well-define what does authentication means? If so, what should an "authentication module" in a source code actually do? I would guess: * Receive an email as input * Receive a password as input * Possibly; receive a username as input * Possibly; receive an encryption private key as input * Possibly; receive a "two factor authentication data" * Possibly; receive a Captcha input