Abstract: According to examples, an apparatus may include a processor that may receive a request from a first device for an authentication token for access to a service, determine whether the first device is authorized to receive the authentication token for access to the service, and based on a determination that the first device is authorized to receive the authentication token for access to the service, generate a machine-readable code including the authentication token that a second device is to use for access to the service by the second device. The processor may also send the generated machine-readable code to the first device. The first device may display the machine-readable code and the second device may use a captured image of the machine-readable code to establish an authenticated session to the service on the second device.

Abstract: According to examples, an apparatus may include a processor that may receive a request from a first device for an authentication token for access to a service, determine whether the first device is authorized to receive the authentication token for access to the service, and based on a determination that the first device is authorized to receive the authentication token for access to the service, generate a machine-readable code including the authentication token that a second device is to use for access to the service by the second device. The processor may also send the generated machine-readable code to the first device. The first device may display the machine-readable code and the second device may use a captured image of the machine-readable code to establish an authenticated session to the service on the second device.

Abstract: Authenticating a secure session between a first user entity and an identity provider using a second user entity. The method includes receiving a request for a session from an entity that purports to be the first user entity. The method further includes sending authentication context from the request, and wherein the authentication context for the request arrives at the second user entity. The method further includes receiving an indication that the authentication context has been verified. As a result, the method further includes authenticating a secure session between a first user entity and an identity provider or approving a secure transaction.

Abstract: Authenticating a secure session between a first user entity and an identity provider using a second user entity. The method includes receiving a request for a session from an entity that purports to be the first user entity. The method further includes sending authentication context from the request, and wherein the authentication context for the request arrives at the second user entity. The method further includes receiving an indication that the authentication context has been verified. As a result, the method further includes authenticating a secure session between a first user entity and an identity provider or approving a secure transaction.

Abstract: Authenticating a secure session between a first user entity and an identity provider using a second user entity. The method includes receiving a request for a session from an entity that purports to be the first user entity. The method further includes sending authentication context from the request, and wherein the authentication context for the request arrives at the second user entity. The method further includes receiving an indication that the authentication context has been verified. As a result, the method further includes authenticating a secure session between a first user entity and an identity provider or approving a secure transaction.

Abstract: Authenticating issues involving the re-authenticating of a first device that was previously authenticated are resolved by use of a second device which receives a notification of the failed authentication. The second device sends a response to the notification which is operable to facilitate re-authentication of the primary device and without requiring the user to provide credentials at the first device prior to obtaining the re-authentication at the primary device and/or without requiring the primary device to obtain a code to be entered into the secondary device and/or prior to the primary device being notified of a failure condition associated with the primary device.

Abstract: Authenticating a secure session between a first user entity and an identity provider using a second user entity. The method receiving a request for a session from an entity that purports to be the first user entity. The method further includes sending authentication context from the request, and wherein the authentication context for the request arrives at the second user entity. The method further includes receiving an indication that the authentication context has been verified. As a result, the method further includes authenticating a secure session between a first user entity and an identity provider or approving a secure transaction.

Abstract: User-authentication-based approval of a first device via communication with a second device over a channel (e.g., an insecure channel) is described. The first device receives a session ID and first user-observable information, or an identifier thereof, from an identity provider, presents the first user-observable information to a user, and sends the session ID to the second device. The second device sends the session ID to the identity provider to obtain therefrom second user-observable information, or an identifier thereof, and a security challenge. The second user-observable information bears a user-discernable relationship to the first user-observable information and is presented to the user by the second device. The second device is capable of generating a response to the security challenge for transmission to the identity provider based at least on input received from the user, the response to the security challenge being indicative of the suitability of the first device for approval.

Abstract: Authenticating issues involving the re-authenticating of a first device that was previously authenticated are resolved by use of a second device which receives a notification of the failed authentication. The second device sends a response to the notification which is operable to facilitate re-authentication of the primary device and without requiring the user to provide credentials at the first device prior to obtaining the re-authentication at the primary device and/or without requiring the primary device to obtain a code to be entered into the secondary device and/or prior to the primary device being notified of a failure condition associated with the primary device.

Abstract: User-authentication-based approval of a first device via communication with a second device over a channel (e.g., an insecure channel) is described. The first device receives a session ID and first user-observable information, or an identifier thereof, from an identity provider, presents the first user-observable information to a user, and sends the session ID to the second device. The second device sends the session ID to the identity provider to obtain therefrom second user-observable information, or an identifier thereof, and a security challenge. The second user-observable information bears a user-discernable relationship to the first user-observable information and is presented to the user by the second device. The second device is capable of generating a response to the security challenge for transmission to the identity provider based at least on input received from the user, the response to the security challenge being indicative of the suitability of the first device for approval.

Abstract: The invention provides a high density package substrate and a method for fabricating the same. A double-sided copper clad laminate containing an upper copper foil and a lower copper foil is provided. A bottom pad is disposed on the lower copper foil, aligned to a predetermined position of a through hole. The through hole is formed by laser drilling through the upper copper foil and the substrate, but not through the bottom pad. A seed layer is formed conformally lining the through hole, and a metal layer is formed on the seed layer by plating to form a plated through hole (PTH).

Abstract: The invention provides a high density package substrate and a method for fabricating the same. A double-sided copper clad laminate containing an upper copper foil and a lower copper foil is provided. A bottom pad is disposed on the lower copper foil, aligned to a predetermined position of a through hole. The through hole is formed by laser drilling through the upper copper foil and the substrate, but not through the bottom pad. A seed layer is formed conformally lining the through hole, and a metal layer is formed on the seed layer by plating to form a plated through hole (PTH).

Abstract: A structure of an integrated packed fuel cell including an integrated cathode electrode sheet that further includes a substrate, at least a cathode electrode area, and at least a conductive opening, an intermediate bonding layer that further includes at least a bonding sheet and at least a conductive opening, an integrated anode electrode sheet that further includes a substrate, at least an anode electrode area, at least a conductive pad, a device combination, and a fuel container base.

Abstract: A novel flat panel DMFC (direct methanol fuel cell) includes an integrated cathode electrode plate, a membrane electrode assembly (MEA) unit, an intermediate bonding layer, an integrated anode electrode plate, and a fuel container. The integrated cathode and anode electrode plates are manufactured by using PCB compatible processes. The integrated cathode and anode electrode plates have embedded metal layout and improved heat dissipation capability.

Abstract: A flat panel direct methanol fuel cell (DMFC) includes an integrated cathode electrode sheet; a membrane electrode assembly (MEA) unit; an intermediate bonding layer; an integrated anode electrode sheet; and a fuel container. The fabrication of the integrated cathode/anode electrode sheets is compatible with printed circuit board (PCB) processes.

Abstract: A flat panel DMFC (direct methanol fuel cell) includes an integrated cathode electrode sheet, a set of membrane electrode assemblies, an intermediate bonding layer, an integrated anode electrode sheet, and a fuel container base. The integrated cathode/anode electrode sheets are manufactured by using PCB compatible processes.

Abstract: A flat panel direct methanol fuel cell (DMFC) includes an integrated cathode electrode plate, a set of membrane electrode assemblies, an intermediate bonding layer, an integrated anode electrode plate, and a fuel container base. The integrated cathode/anode electrode plates are conducive to mass production, and are manufactured by using PCB compatible processes.

Abstract: A flat panel DMFC (direct methanol fuel cell) includes a first electrode plate, a set of membrane assemblies, at least a bonding sheet, a second electrode, and fuel container base. Because of the gap between the first/second electrode plates and the membrane assembly when they are laminated, the present invention provides a method to improve the contact between the first/second electrode plates and the membrane assembly.

Abstract: A flat panel DMFC (direct methanol fuel cell) includes a first electrode plate, a set of membrane assemblies, at least a bonding sheet, a second electrode, and fuel container base. Because of the gap between the first/second electrode plates and the membrane assembly when they are laminated, the present invention provides a method to improve the contact between the first/second electrode plates and the membrane assembly.

Abstract: A flat panel direct methanol fuel cell (DMFC) includes an integrated cathode electrode sheet; a membrane electrode assembly (MEA) unit; an intermediate bonding layer; an integrated anode electrode sheet; and a fuel container. The fabrication of the integrated cathode/anode electrode sheets is compatible with printed circuit board (PCB) processes.