Re: [pkcs11] Groups - pkcs11-base-v2.40-loginuser-v1-changes.pdf uploaded

This simply fixes the existing practice of jamming a username into the PIN parameter of C_Login.
Setting up usernames remains outside the proposal (as it is currently) - I had no plans to tackle that particular can of worms when fixing this specific issue - i.e. C_InitPIN and C_SetPIN remain unchanged.

The typical use that is out there does not abuse the parameters in C_InitPIN and C_SetPIN hence why I didn't suggest changing those.

Tim.

On Thu, Apr 13, 2017 at 9:01 AM, Mark Joseph <> wrote:

This is a much needed addition to the PKCS#11 API.   I must of missed it but how is the "user name" created in a token in the first place?   Is there a corresponding update to the C_SetPIN operation?

Thanks,

Mark Joseph

P6R, Inc

From:

 
Tim Hudson <>

To:

 
<>

Sent:
 

4/12/2017 2:15 PM

Subject:

 
[pkcs11] Groups - pkcs11-base-v2.40-loginuser-v1-changes.pdf uploaded

Submitter's message

        Note: everywhere that C_Login is referenced elsewhere in the text it is changed to C_Login or C_LoginUser - allowing that either can be used. 

A word version with those changes applied can be uploaded if anyone wants to look at it.
        

-- Tim Hudson
        
    

    
        Document Name: pkcs11-base-v2.40-loginuser-v1-changes.pdf

        
        Description

        C_LoginUser text to match mailing list proposal.

This is simply the same as C_Login only allowing the username to be

provided as a separate parameter instead of being jammed into the PIN

parameter (current practice).        

        Download Latest Revision

        Public Download Link
        
        Submitter: Tim Hudson

                Group: OASIS PKCS 11 TC

        Folder: Working Drafts

        Date submitted: 2017-04-12 14:15:15