Method, apparatus, and system for identity authentication
US-10038554-B2 · Jul 31, 2018 · US
US2025298908A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2025298908-A1 |
| Application number | US-202418612985-A |
| Country | US |
| Kind code | A1 |
| Filing date | Mar 21, 2024 |
| Priority date | Mar 21, 2024 |
| Publication date | Sep 25, 2025 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Apparatuses, systems, and techniques to perform an application programming interface (API). In at least one embodiment, said API is to cause information to be encrypted based, at least in part, on one or more encryption algorithm indicators.
Opening claim text (preview).
What is claimed is: 1 . A processor comprising: one or more circuits to perform an application programming interface (API) to cause information to be encrypted based, at least in part, on one or more encryption algorithm indicators. 2 . The processor according to claim 1 , wherein the one or more encryption algorithm indicators are to identify one or more salts. 3 . The processor according to claim 1 , wherein performing the API is to further cause a mapping of encryption algorithm identifiers to salts to be generated. 4 . The processor according to claim 1 , wherein the one or more encryption algorithm indicators comprise one or more opaque identifiers associated with one or more encryption algorithms. 5 . The processor according to claim 1 , wherein the one or more encryption algorithm indicators identify one or more salts usable to encrypt the information. 6 . The processor according to claim 1 , wherein the one or more encryption algorithm indicators identify cryptographic information usable to encrypt the information, and wherein the cryptographic information is inaccessible outside of software to use the information. 7 . The processor according to claim 1 , wherein performing the API is to cause the information to be encrypted such that, to decrypt the information, at least both cryptographic information accessible to a user and cryptographic information inaccessible outside of software to use the information are to be used. 8 . The processor according to claim 1 , wherein performing the API is to further cause the information to be encrypted using at least both a key of a user and an encryption algorithm identified by the one or more encryption algorithm indicators. 9 . A method comprising: performing an application programming interface (API) to cause information to be encrypted based, at least in part, on one or more encryption algorithm indicators. 10 . The method according to claim 9 , wherein the one or more encryption algorithm indicators are to identify one or more salts. 11 . The method according to claim 9 , wherein performing the API is to further cause a mapping of encryption algorithm identifiers to salts to be generated. 12 . The method according to claim 9 , wherein the one or more encryption algorithm indicators comprise one or more opaque identifiers associated with one or more encryption algorithms. 13 . The method according to claim 9 , wherein the one or more encryption algorithm indicators identify one or more salts usable to encrypt the information. 14 . The method according to claim 9 , wherein the one or more encryption algorithm indicators identify cryptographic information usable to encrypt the information, and wherein the cryptographic information is inaccessible outside of software to use the information. 15 . A system comprising: one or more processors to perform an application programming interface (API) to cause information to be encrypted based, at least in part, on one or more encryption algorithm indicators. 16 . The system according to claim 15 , wherein the one or more encryption algorithm indicators are to identify one or more salts. 17 . The system according to claim 15 , wherein performing the API is to further cause a mapping of encryption algorithm identifiers to salts to be generated. 18 . The system according to claim 15 , wherein the one or more encryption algorithm indicators comprise one or more opaque identifiers associated with one or more encryption algorithms. 19 . The system according to claim 15 , wherein the one or more encryption algorithm indicators identify one or more salts usable to encrypt the information. 20 . The system according to claim 15 , wherein performing the API is to cause the information to be encrypted such that, to decrypt the information, at least both cryptographic information accessible to a user and cryptographic information inaccessible outside of software to use the information are to be used.
to a system of files or objects, e.g. local or distributed file system or database · CPC title
Providing cryptographic facilities or services · CPC title
Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms (network architectures or network communication protocols for using time-dependent keys in a packet data network H04L63/068) · CPC title
involving passwords or one-time passwords (network architectures or network communication protocols for using one-time keys in a packet data network H04L63/067) · CPC title
Interprogram communication · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.