439
edits
NSS Shared DB: Difference between revisions
→Shared Database Proposal
| Line 473: | Line 473: | ||
This will not be necessary if the merge operation has already completed, | This will not be necessary if the merge operation has already completed, | ||
or if the source DB had no password. To determine this, the application | or if the source DB had no password. To determine this, the application | ||
calls a function to ask if the token in the DB slot is removable. | calls a function to ask if the token in the DB slot is removable. '''FIX ME'' The | ||
function to be called for that purpose has not yet been made public, so | function to be called for that purpose has not yet been made public, so | ||
those details are TBD. That needs to be corrected. | those details are TBD. That needs to be corrected. | ||
| Line 484: | Line 484: | ||
a) (optional) Call PK11_GetTokenName to get the name of the token. With | a) (optional) Call PK11_GetTokenName to get the name of the token. With | ||
that name, you can be sure that you are authenticating to the source token. | that name, you can be sure that you are authenticating to the source token. Skipping this step is not harmful, it is only necessary if the application absolutely needs to know which token the following PK11_Authenticate() will be called on. For most NSS applications the underlying password prompt system will properly disambiguate the appropriate password to the user. | ||
b) Call PK11_Authenticate() to authenticate to the source token. This | b) Call PK11_Authenticate() to authenticate to the source token. This | ||
| Line 490: | Line 490: | ||
function to retrieve the password. | function to retrieve the password. | ||
If this step fails: stop. A Failure at this point is described | If this step fails: stop. A Failure at this point is described below as "Exception A". | ||
Otherwise, continue with step 4. | Otherwise, continue with step 4. | ||
| Line 507: | Line 506: | ||
If this fails, stop. | If this fails, stop. | ||
If this call indicates that the token is NOT present, | If this call indicates that the token is NOT present, something fundamentally wrong in the NSS softoken engine. Applications should treat this the same as | ||
an NSS initialization failure. | |||
If this call indicates that the token name in the DB slot is now the | If this call indicates that the token name in the DB slot is now the | ||
target token name, continue to step 6. | target token name, continue to step 6. | ||
| Line 516: | Line 515: | ||
step will be to authenticate to the target DB token. This call allows | step will be to authenticate to the target DB token. This call allows | ||
the caller to ensure that he is about the authenticate to the target | the caller to ensure that he is about the authenticate to the target | ||
token, and to get the target token name string for prompts. | token, and to get the target token name string for prompts. NOTE: Again, this check is only necessary form applications which need to know exactly which password PK11_Authenticate() is prompting for. For most well written NSS applications this step is not needed. | ||
Step 7: Call PK11_Authenticate to authenticate to the target token. | Step 7: Call PK11_Authenticate to authenticate to the target token. | ||
| Line 522: | Line 521: | ||
callback function to retrieve the password. | callback function to retrieve the password. | ||
If this step fails: stop. A Failure at this point is described | If this step fails: stop. A Failure at this point is described below as "Exception B". | ||
Otherwise, continue with step 8. | Otherwise, continue with step 8. | ||
| Line 529: | Line 527: | ||
The Source DB Unique identifier string will have been written into the | The Source DB Unique identifier string will have been written into the | ||
target DB, so that future attempts to merge the same DB will be detected | target DB, so that future attempts to merge the same DB will be detected | ||
and avoided. | and avoided. Your application can continue forward using NSS. NSS will use the merged shared database for all it's database operations from this point forward. | ||
A | Exeptions: | ||
exception A. Application needs to decide what happens if the legacy password | |||
is not supplied. Application can choose to: | |||
# continue to use the legacy DB and try to update later. | |||
# force NSS to mark legacy DB to be updated without actually updating the legacy DB (throwing away everything in the legacy DB). | |||
# force NSS to update those objects it can from the legacy DB, throwing | |||
away private keys and saved passwords. | |||
exception B. Applications needs to decide what happens if the new shared DB | |||
password is not supplied. Application can choose to: | |||
# continue to use the legacy DB and try to update later. | |||
# force NSS to mark legacy DB to be updated without actually updating the legacy DB (throwing away everything in the legacy DB). | |||
# force NSS to update those objects it can from the legacy DB,throwing away private keys and saved passwords, and trust information from the legacy DB. | |||
# force NSS to reset the shared database password, throwing away private keys and saved passwords, and trust information rom the shared DB. | |||
Note 1: The actual merger may take place during step 1, or step 3b, or | Note 1: The actual merger may take place during step 1, or step 3b, or | ||
step 7; that is, during the call to NSS_InitWithMerge or during either | step 7; that is, during the call to NSS_InitWithMerge or during either | ||
| Line 551: | Line 560: | ||
string in the target DB and act as if the merger is complete. This is similiar to what happens in all previous versions of NSS during database update. See "Database Merge" below for how to recover from this. | string in the target DB and act as if the merger is complete. This is similiar to what happens in all previous versions of NSS during database update. See "Database Merge" below for how to recover from this. | ||
==== Database Upgrade Underlying Implementation = | ====== Database Upgrade Underlying Implementation ====== | ||
Upgrade complications only affect Type A applications. In order to merge a | Upgrade complications only affect Type A applications. In order to merge a | ||
| Line 750: | Line 758: | ||
done | done | ||
===== Merge Conflicts (Mode 3A only) ===== | ===== Merge Conflicts (Mode 3A only) ===== | ||
| Line 950: | Line 939: | ||
===== Database Merge ===== | ===== Database Merge ===== | ||
While not necessarily a feature of shared database, it is an important tool for successful shared database deployments. | |||
==== Layering ==== | ==== Layering ==== | ||