MétaCan
Menu
Back to cohort
Record W1995054968 · doi:10.1145/1321211.1321229

Client certificate and IP address based multi-factor authentication for J2EE web applications

2007· article· en· W1995054968 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueProceedings of CASCON · 2007
Typearticle
Languageen
FieldSocial Sciences
TopicAccess Control and Trust
Canadian institutionsnot available
Fundersnot available
KeywordsComputer scienceAuthentication (law)CertificateRoot certificateMulti-factor authenticationWeb application securityWeb applicationFactor (programming language)World Wide WebPublic key certificateComputer securityComputer networkWeb serviceAuthentication protocolWeb developmentPublic-key cryptographyEncryption

Abstract

fetched live from OpenAlex

Secure and encrypted authentication is an important aspect of J2EE web application security. SSL client certificate authentication provides an encrypted log-on mechanism and a single sign-on capability that does not involve the use of passwords. Unlike SPNEGO-protocol-based Kerberos authentication, which requires both parties to be in the same domain, client certificate authentication works across domain boundaries as long as the user registry for the application server is properly set up to handle the certificate. But client certificate authentication comes with some shortcomings---especially when the client certificate is used from an unauthorized machine. We will examine this potential vulnerability of client certificate authentication and show how to make this type of authentication more secure by using multi-factor authentication. Adding an IP-address-checking servlet filter to the web application is one good approach. We will provide implementation details as well.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.405
Threshold uncertainty score0.299

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.102
GPT teacher head0.365
Teacher spread0.263 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it