summaryrefslogtreecommitdiffstats
path: root/security/nss/doc/rst/legacy/reference/fc_opensession/index.rst
blob: 23c6927ed8dc96860a16c34b050287f2e54b9ba5 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
.. _mozilla_projects_nss_reference_fc_opensession:

FC_OpenSession
==============

`Name <#name>`__
~~~~~~~~~~~~~~~~

.. container::

   FC_OpenSession - open a session between an application and a token.

`Syntax <#syntax>`__
~~~~~~~~~~~~~~~~~~~~

.. container::

   .. code::

      CK_RV FC_OpenSession(
        CK_SLOT_ID slotID,
        CK_FLAGS flags,
        CK_VOID_PTR pApplication,
        CK_NOTIFY Notify,
        CK_SESSION_HANDLE_PTR phSession
      );

`Parameters <#parameters>`__
~~~~~~~~~~~~~~~~~~~~~~~~~~~~

.. container::

   ``FC_OpenSession`` has the following parameters:

   ``slotID``
      [in] the ID of the token's slot.
   ``flags``
      [in]
   ``pApplication``
   ``Notify``
      [in] pointer to a notification callback function. Not currently supported.
   ``phSession``
      [out] pointer to a session handle.

`Description <#description>`__
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

.. container::

   ``FC_OpenSession`` opens a session between an application and the token in the slot with the ID
   ``slotID``.

   The NSS cryptographic module currently doesn't call the surrender callback function ``Notify``.
   (See PKCS #11 v2.20 section 11.17.1.)

   A user may call ``FC_OpenSession`` without logging into the token (to assume the NSS User role).

.. _return_value:

`Return value <#return_value>`__
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

.. container::

`Examples <#examples>`__
~~~~~~~~~~~~~~~~~~~~~~~~

.. container::

.. _see_also:

`See also <#see_also>`__
~~~~~~~~~~~~~~~~~~~~~~~~

.. container::

   -  :ref:`mozilla_projects_nss_reference_fc_closesession`,
      `NSC_OpenSession </en-US/NSC_OpenSession>`__