1. A coated article, comprising:
a substrate being made of aluminum alloy or magnesium alloy;
an anti-corrosion layer formed on the substrate, the anti-corrosion layer being an amorphous alloy layer and containing about 68% to about 72% of iron, about 8% to about 12% of chromium, about 10% to about 14% of boron, and about 2% to about 14% of M by atomic percentage; and
a decorative layer directly formed on and contacting the anti-corrosion layer;
wherein M being one or more selected from the group consisting of phosphorus, carbon and silicon.
2. The coated article as claimed in claim 1, wherein the anti-corrosion layer has a thickness of about 800 nm to about 1200 nm.
3. The coated article as claimed in claim 1, wherein the decorative layer is composed of a compound selected from the group consisting of carbide of titanium, chromium or zirconium, nitride of titanium, chromium or zirconium, and oxide of titanium, chromium or zirconium.
4. The coated article as claimed in claim 1, wherein the decorative layer has a thickness of about 400 nm to about 600 nm.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A computer-implemented method for converting authentication-tokens, comprising:
receiving, at a computer, a command-execution request from a first application, wherein the command-execution request specifies a command to be executed by a second application and includes a first authentication-token that is created by the first application based on a user authenticating to the first application;
verifying the first authentication-token at the computer;
translating the first authentication-token to a form associated with the second application to produce a second authentication-token, wherein the second authentication-token is in a form different than the first authentication-token;
modifying the command-execution request by replacing the first authentication-token with the second authentication-token to create a modified command-execution request; and
sending the modified command-execution request to the second application,
wherein the command-execution request includes a target Uniform Resource Locator (URL) which specifies a location of the second application, a second authentication-token type which specifies a form of the second authentication-token, a user identifier for a user who is associated with the first authentication-token, and payload data for the second application.
2. The method of claim 1, wherein the first application is located on the same computer system as the second application.
3. The method of claim 1, wherein the command-execution request comprises a first authentication-token type which specifies a form of the first authentication-token.
4. The method of claim 1, wherein verifying the first authentication-token further comprises:
identifying a first authentication-token type for the first authentication-token;
using decryption rules associated with the first authentication-token type to decrypt the first authentication-token to produce a decrypted first authentication-token; and
verifying the validity of the decrypted first authentication-token.
5. The method of claim 4, wherein verifying the validity of the decrypted first authentication-token can involve:
verifying that the decrypted first authentication-token has not expired; and
verifying that the decrypted first authentication-token is associated with a user identifier.
6. The method of claim 1, wherein translating the first authentication-token further comprises:
identifying the second authentication-token type;
identifying a second user identifier which is mapped from the user identifier; and
creating the second authentication-token associated with the second user identifier, wherein the second authentication-token is of the form specified by the second-authentication-token type.
7. The method of claim 6, wherein creating the second authentication-token can involve:
requesting the second authentication-token from a third-party authentication-token provider; and
receiving the second authentication-token from the third-party authentication-token provider.
8. The method of claim 6, wherein the second user identifier comprises the user identifier.
9. The method of claim 1, wherein the first authentication-token and the second authentication-token include one or more of:
a cookie;
a digital certificate;
a user-namepassword pair;
a cryptographic key; and
a biometric identifier.
10. The method of claim 1, wherein modifying the command-execution request further comprises:
modifying a format of the command to a format associated with the second application; and
including the modified command with the modified command-execution request.
11. A non-transitory computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for converting authentication-tokens, the method comprising:
receiving, at a bridge, a command-execution request from a first application, wherein the command-execution request specifies a command to be executed by a second application and includes a first authentication-token that is created by the first application based on a user authenticating to the first application;
verifying the first authentication-token at the bridge;
translating the first authentication-token to a form associated with the second application to produce a second authentication-token, wherein the second authentication-token is in a form different than the first authentication-token;
modifying the command-execution request by replacing the first authentication-token with the second authentication-token to create a modified command-execution request; and
sending the modified command-execution request to the second application,
wherein the command-execution request includes a target Uniform Resource Locator (URL) which specifies a location of the second application, a second authentication-token type which specifies a form of the second authentication-token, a user identifier for a user who is associated with the first authentication-token, and payload data for the second application.
12. The computer-readable storage medium of claim 11, wherein the first application is located on the same computer system as the second application.
13. The computer-readable storage medium of claim 11, wherein the command-execution request comprises a first authentication-token type which specifies a form of the first authentication-token.
14. The computer-readable storage medium of claim 11, wherein verifying the first authentication-token further comprises:
identifying a first authentication-token type for the first authentication-token;
using decryption rules associated with the first authentication-token type to decrypt the first authentication-token to produce authentication-token; and
verifying the validity of the decrypted first authentication-token.
15. The computer-readable storage medium of claim 14, wherein verifying the validity of the decrypted first authentication-token can involve:
verifying that the decrypted first authentication-token has not expired; and
verifying that the decrypted first authentication-token is associated with a user identifier.
16. The computer-readable storage medium of claim 11, wherein translating the first authentication-token further comprises:
identifying the second authentication-token type;
identifying a second user identifier which is mapped from and the user identifier; and
creating the second authentication-token associated with the second user identifier, wherein the second authentication-token is of the form specified by the second-authentication-token type.
17. The computer-readable storage medium of claim 16, wherein creating the second authentication-token can involve:
requesting the second authentication-token from a third-party authentication-token provider; and
receiving the second authentication-token from the third-party authentication-token provider.
18. The computer-readable storage medium of claim 16, wherein the second user identifier comprises the user identifier.
19. The computer-readable storage medium of claim 11, wherein the first authentication-token and the second authentication-token include one or more of:
a cookie;
a digital certificate;
a user-namepassword pair;
a cryptographic key; and
a biometric identifier.
20. The computer-readable storage medium of claim 11, wherein modifying the command-execution request further comprises:
modifying a format of the command to a format associated with the second application; and
including the modified command with the modified command-execution request.
21. An apparatus that converts authentication-tokens, comprising:
a receiving mechanism configured to receive, at a bridge, a command-execution request from a first application, wherein the command-execution request specifies a command to be executed by a second application and includes a first authentication-token that is created by the first application based on a user authenticating to the first application;
a verification mechanism configured to verify the first authentication token at the bridge;
a translation mechanism configured to translate the first authentication-token to a form associated with the second application to produce a second authentication-token, wherein the second authentication-token is in a form different than the first authentication-token;
a modification mechanism configured to modify the command-execution request by replacing the first authentication-token with the second authentication-token to create a modified command-execution request; and
a sending mechanism configured to send the modified command-execution request to the second application,
wherein the command-execution request includes a target Uniform Resource Locator (URL) which specifies a location of the second application, a second authentication-token type which specifies a form of the second authentication-token, a user identifier for a user who is associated with the first authentication-token, and payload data for the second application.
22. The apparatus of claim 21, wherein the verification mechanism further comprises:
an identification mechanism configured to identify a first authentication-token type for the first authentication-token;
a decryption mechanism configured to use decryption rules associated with the first authentication-token type to decrypt the first authentication-token to produce a decrypted first authentication-token; and
a second verification mechanism configured to verify the validity of the decrypted first authentication-token.
23. The apparatus of claim 21, wherein the translation mechanism further comprises:
an identification mechanism configured to identify the second authentication-token type;
a second identification mechanism configured to identify a second user identifier which is mapped from and the user identifier; and
a creation mechanism configured to create the second authentication-token associated with the second user identifier, wherein the second authentication-token is of the form specified by the second-authentication-token type.
24. The apparatus of claim 22, wherein the second verification mechanism is further configured to:
verify that the decrypted first authentication-token has not expired; and to
verify that the decrypted first authentication-token is associated with a user identifier.
25. The apparatus of claim 23, wherein the creation mechanism further comprises:
a requesting mechanism configured to request the second authentication-token from a third-party authentication-token provider; and
a receiving mechanism configured to receive the second authentication-token from the third-party authentication-token provider.
26. The apparatus of claim 21, wherein the modification mechanism is further configured to:
modify a format of the command to a format associated with the second application; and to
include the modified command with the modified command-execution request.