Cadillac at 00:24, 23 August 2021

2021-08-23T00:24:49Z

← Older revision		Revision as of 20:24, 22 August 2021
Line 22:		Line 22:
	# Hash check (handled by sheme + hash method)		# Hash check (handled by sheme + hash method)
	An auth scheme CAN do stuff outside these three steps, but only using it's own external files.		An auth scheme CAN do stuff outside these three steps, but only using it's own external files.

			[[Category:Development]]

Epsy: New page: {{Blueprint|aagid2}} '''AAGID''' is a specification that defines an authentication scheme originally designed to work with Armagetron Advanced. It is therefore probably suitable for use i...

2008-09-13T18:38:54Z

New page: {{Blueprint|aagid2}} '''AAGID''' is a specification that defines an authentication scheme originally designed to work with Armagetron Advanced. It is therefore probably suitable for use i...

New page

{{Blueprint|aagid2}}

'''AAGID''' is a specification that defines an authentication scheme originally designed to work with Armagetron Advanced. It is therefore probably suitable for use in other games. Additionally, some interfaces were done in order to have it working on websites around the community, to keep in line with the only one login goal.

'''AAGID''' stands for '''A'''rmagetron '''A'''dvanced '''G'''lobal '''ID'''entifier.

This specifications does NOT specify the way the authenticating user and the server communicate!

==The need for a "v2"==
The first version of what I call AAGID was kind of a mix between what's on [[Hash Based Authentication]] and [[Web Authentication]]. The only really complete documentation was the source code itself. That's a huge issue regarding expansion and overall clarity.

[[Web Authentication]] implementations made the need for a way to handle different authentication schemes apparent. This version will define a way to negotiate schemes as well as hash methods between the server and the authority.

Also, this fixes some annoyances, such as lists being separated by either spaces or commas, or even both, which is a pain to parse when you don't read the string character by character.

While it lets room for new schemes or hash methods, this specification also defines the aa and webform schemes. However these two schemes are still not mandatory.

==Overview==
An authentication process with AAGID is always done in the three following steps:
# Authentication scheme/hash method negotiation
# Prerequisites (handled by scheme)
# Hash check (handled by sheme + hash method)
An auth scheme CAN do stuff outside these three steps, but only using it's own external files.

AAGID v0.2 - Revision history

Cadillac at 00:24, 23 August 2021

Epsy: New page: {{Blueprint|aagid2}} '''AAGID''' is a specification that defines an authentication scheme originally designed to work with Armagetron Advanced. It is therefore probably suitable for use i...