Parents (Total: 9)

The searched file hash is included in 9 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	66A122FAB0DE0F1AC888CEE6C898B544
PackageArch	noarch
PackageDescription	The authentication plugin provides generic user support for Catalyst apps. It is the basis for both authentication (checking the user is who they claim to be), and authorization (allowing the user to do what the system authorises them to do). Using authentication is split into two parts. A Store is used to actually store the user information, and can store any amount of data related to the user. Credentials are used to verify users, using information from the store, given data from the frontend. A Credential and a Store are paired to form a 'Realm'. A Catalyst application using the authentication framework must have at least one realm, and may have several. To implement authentication in a Catalyst application you need to add this module, and specify at least one realm in the configuration. Authentication data can also be stored in a session, if the application is using the Catalyst::Plugin::Session module. *NOTE* in version 0.10 of this module, the interface to this module changed. Please see COMPATIBILITY ROUTINES for more information.
PackageName	perl-Catalyst-Plugin-Authentication
PackageRelease	lp153.2.11
PackageVersion	0.10023
SHA-1	9737DE962985DA5765BD7F80C9CFE85F2F1C303A
SHA-256	0E111C091475E13346A4C8CEDE7AF03C551437FC51D6F029EF6C4F6B88E77195

Key	Value
MD5	0FD36D452D2D3D844B5C5BEE4A894887
PackageArch	noarch
PackageDescription	The authentication plugin provides generic user support for Catalyst apps. It is the basis for both authentication (checking the user is who they claim to be), and authorization (allowing the user to do what the system authorises them to do). Using authentication is split into two parts. A Store is used to actually store the user information, and can store any amount of data related to the user. Credentials are used to verify users, using information from the store, given data from the frontend. A Credential and a Store are paired to form a 'Realm'. A Catalyst application using the authentication framework must have at least one realm, and may have several. To implement authentication in a Catalyst application you need to add this module, and specify at least one realm in the configuration. Authentication data can also be stored in a session, if the application is using the Catalyst::Plugin::Session module. *NOTE* in version 0.10 of this module, the interface to this module changed. Please see COMPATIBILITY ROUTINES for more information.
PackageName	perl-Catalyst-Plugin-Authentication
PackageRelease	2.7
PackageVersion	0.10023
SHA-1	8381BC423A8C1F291CEED4E739FB77E0DEA7489C
SHA-256	4B2882413F1DDCC612933048A4AA4ECF0154AB38A912EF9C4DAD05508B462E5D

Key	Value
MD5	7B19261375A97D91E389479ADDBF42E6
PackageArch	noarch
PackageDescription	The authentication plugin provides generic user support for Catalyst apps. It is the basis for both authentication (checking the user is who they claim to be), and authorization (allowing the user to do what the system authorises them to do). Using authentication is split into two parts. A Store is used to actually store the user information, and can store any amount of data related to the user. Credentials are used to verify users, using information from the store, given data from the frontend. A Credential and a Store are paired to form a 'Realm'. A Catalyst application using the authentication framework must have at least one realm, and may have several. To implement authentication in a Catalyst application you need to add this module, and specify at least one realm in the configuration. Authentication data can also be stored in a session, if the application is using the Catalyst::Plugin::Session module. *NOTE* in version 0.10 of this module, the interface to this module changed. Please see COMPATIBILITY ROUTINES for more information.
PackageName	perl-Catalyst-Plugin-Authentication
PackageRelease	2.47
PackageVersion	0.10023
SHA-1	574F65F5A282428E9CFBDED6423A62CD3D3916EF
SHA-256	7A21711E1B8224B20DF39B3AC64876333B71989552CB6A830F4CE45440FFFCD4

Key	Value
MD5	4B82F6E75BC54852CE0F1012778858AF
PackageArch	noarch
PackageDescription	The authentication plugin provides generic user support for Catalyst apps. It is the basis for both authentication (checking the user is who they claim to be), and authorization (allowing the user to do what the system authorises them to do). Using authentication is split into two parts. A Store is used to actually store the user information, and can store any amount of data related to the user. Credentials are used to verify users, using information from the store, given data from the frontend. A Credential and a Store are paired to form a 'Realm'. A Catalyst application using the authentication framework must have at least one realm, and may have several. To implement authentication in a Catalyst application you need to add this module, and specify at least one realm in the configuration. Authentication data can also be stored in a session, if the application is using the Catalyst::Plugin::Session module. *NOTE* in version 0.10 of this module, the interface to this module changed. Please see COMPATIBILITY ROUTINES for more information.
PackageName	perl-Catalyst-Plugin-Authentication
PackageRelease	lp151.2.1
PackageVersion	0.10023
SHA-1	A3C0A48D68814273FDF349FA103B7EAC3D127D47
SHA-256	C0F1CAC6E3FE5680F469DC55489B9612B95BBD7D017AB8A67894235BF0B167C8

Key	Value
MD5	A7A71E88F13E056202E93A9E49293C36
PackageArch	noarch
PackageDescription	The authentication plugin provides generic user support for Catalyst apps. It is the basis for both authentication (checking the user is who they claim to be), and authorization (allowing the user to do what the system authorises them to do). Using authentication is split into two parts. A Store is used to actually store the user information, and can store any amount of data related to the user. Credentials are used to verify users, using information from the store, given data from the frontend. A Credential and a Store are paired to form a 'Realm'. A Catalyst application using the authentication framework must have at least one realm, and may have several. To implement authentication in a Catalyst application you need to add this module, and specify at least one realm in the configuration. Authentication data can also be stored in a session, if the application is using the Catalyst::Plugin::Session module. *NOTE* in version 0.10 of this module, the interface to this module changed. Please see COMPATIBILITY ROUTINES for more information.
PackageName	perl-Catalyst-Plugin-Authentication
PackageRelease	lp152.2.1
PackageVersion	0.10023
SHA-1	91DC49421BE17977CA9DEE03B677481A5C1C01FF
SHA-256	128EE8D7B57F2DBBAF0F4FA1825233F824916C78450A0A025247EEB6351E0AD9

Key	Value
MD5	4C502D34E4958F43C6454DD0CB9AFDC8
PackageArch	noarch
PackageDescription	The authentication plugin provides generic user support for Catalyst apps. It is the basis for both authentication (checking the user is who they claim to be), and authorization (allowing the user to do what the system authorises them to do). Using authentication is split into two parts. A Store is used to actually store the user information, and can store any amount of data related to the user. Credentials are used to verify users, using information from the store, given data from the frontend. A Credential and a Store are paired to form a 'Realm'. A Catalyst application using the authentication framework must have at least one realm, and may have several. To implement authentication in a Catalyst application you need to add this module, and specify at least one realm in the configuration. Authentication data can also be stored in a session, if the application is using the Catalyst::Plugin::Session module. *NOTE* in version 0.10 of this module, the interface to this module changed. Please see COMPATIBILITY ROUTINES for more information.
PackageName	perl-Catalyst-Plugin-Authentication
PackageRelease	lp150.2.1
PackageVersion	0.10023
SHA-1	1CAEF4ECE23D414F321F20E5233D774AFFA30A5D
SHA-256	961F7820715AD7840C44EB3D39A189B8CC5403784A084273794BDB8776544904

Key	Value
MD5	E9AE40D9B087DC62AAEF8E29EE376274
PackageArch	noarch
PackageDescription	The authentication plugin provides generic user support for Catalyst apps. It is the basis for both authentication (checking the user is who they claim to be), and authorization (allowing the user to do what the system authorises them to do). Using authentication is split into two parts. A Store is used to actually store the user information, and can store any amount of data related to the user. Credentials are used to verify users, using information from the store, given data from the frontend. A Credential and a Store are paired to form a 'Realm'. A Catalyst application using the authentication framework must have at least one realm, and may have several. To implement authentication in a Catalyst application you need to add this module, and specify at least one realm in the configuration. Authentication data can also be stored in a session, if the application is using the Catalyst::Plugin::Session module. *NOTE* in version 0.10 of this module, the interface to this module changed. Please see COMPATIBILITY ROUTINES for more information.
PackageName	perl-Catalyst-Plugin-Authentication
PackageRelease	2.41
PackageVersion	0.10023
SHA-1	9D34E0F020BD92B4051B2CE8E46BCB3DC42822EF
SHA-256	C4C69E15CFDF02226AF1AF30D955FC833E329D3D3FFBF4437D6D8565B32BDB55

Key	Value
MD5	B858F6CFA5696943952FA706D63AAB26
PackageArch	noarch
PackageDescription	The authentication plugin provides generic user support for Catalyst apps. It is the basis for both authentication (checking the user is who they claim to be), and authorization (allowing the user to do what the system authorises them to do). Using authentication is split into two parts. A Store is used to actually store the user information, and can store any amount of data related to the user. Credentials are used to verify users, using information from the store, given data from the frontend. A Credential and a Store are paired to form a 'Realm'. A Catalyst application using the authentication framework must have at least one realm, and may have several. To implement authentication in a Catalyst application you need to add this module, and specify at least one realm in the configuration. Authentication data can also be stored in a session, if the application is using the Catalyst::Plugin::Session module. *NOTE* in version 0.10 of this module, the interface to this module changed. Please see COMPATIBILITY ROUTINES for more information.
PackageName	perl-Catalyst-Plugin-Authentication
PackageRelease	2.2
PackageVersion	0.10023
SHA-1	1D0A4ED369934F7B631EA3476676F7066FE094DB
SHA-256	FD72CAF3802888D9FB6C445B0C9A61F4A664132E8C8949D6AE83CFD980BE78A1

Key	Value
MD5	46065C87D9AC94F2822AB2C13654D8F0
PackageArch	noarch
PackageDescription	The authentication plugin provides generic user support for Catalyst apps. It is the basis for both authentication (checking the user is who they claim to be), and authorization (allowing the user to do what the system authorises them to do). Using authentication is split into two parts. A Store is used to actually store the user information, and can store any amount of data related to the user. Credentials are used to verify users, using information from the store, given data from the frontend. A Credential and a Store are paired to form a 'Realm'. A Catalyst application using the authentication framework must have at least one realm, and may have several. To implement authentication in a Catalyst application you need to add this module, and specify at least one realm in the configuration. Authentication data can also be stored in a session, if the application is using the Catalyst::Plugin::Session module. *NOTE* in version 0.10 of this module, the interface to this module changed. Please see COMPATIBILITY ROUTINES for more information.
PackageName	perl-Catalyst-Plugin-Authentication
PackageRelease	2.1
PackageVersion	0.10023
SHA-1	3941EE73BAC8B8B6526A8FC048950C10D69A3B8F
SHA-256	8FA8837E49D5BD50B25CEFF7FFE4941F5ECA34D94F2E43E2CE88F6F7F5FDD56E