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
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
|
%global _empty_manifest_terminate_build 0
Name: python-velruse
Version: 1.1.1
Release: 1
Summary: Simplifying third-party authentication for web applications.
License: UNKNOWN
URL: http://velruse.readthedocs.org/en/latest/index.html
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/9c/d9/e18b5c98667c45f5dd1a256d72168ea5ff68f0025fc5b24be010f2696ca3/velruse-1.1.1.tar.gz
BuildArch: noarch
%description
Overview
Velruse aims to simplify authenticating a user. It provides auth
providers that handle authenticating to a variety of identity providers
with multiple authentication schemes (LDAP, SAML, etc.).
Eventually, Velruse will include widgets similar to RPXNow that allow
one to customize a login/registration widget so that a website user can
select a preferred identity provider to use to sign-in.
In the mean-time, effort is focused on increasing the available auth
providers for the commonly used authentication schemes and identity
providers (Facebook, Google, OpenID, etc).
Unlike other authentication libraries for use with web applications, a
website using Velruse for authentication does not have to be written in
any particular language.
API
Velruse implements an API similar to RPXNow to standardize the way a
web application handles user authentication.
Velruse Authentication flow
1. Website sends a POST to the auth provider‘s URL with an endpoint that
the user should be redirected back to when authentication is complete
and includes any additional parameters that the auth provider requires.
2. When the auth provider finishes the authentication, the user is
redirected back to the endpoint specified with a POST, which includes
a unique token.
3. Website then makes a query to the UserStore using the token that was
provided. The user’s identity information will be returned, or an
error if the authentication was unsuccessful.
If the website is unable to directly access the UserStore then Step 3 can
be replaced by issuing a HTTP POST in the background to the auth provider
requesting the user’s information with the token.
%package -n python3-velruse
Summary: Simplifying third-party authentication for web applications.
Provides: python-velruse
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-velruse
Overview
Velruse aims to simplify authenticating a user. It provides auth
providers that handle authenticating to a variety of identity providers
with multiple authentication schemes (LDAP, SAML, etc.).
Eventually, Velruse will include widgets similar to RPXNow that allow
one to customize a login/registration widget so that a website user can
select a preferred identity provider to use to sign-in.
In the mean-time, effort is focused on increasing the available auth
providers for the commonly used authentication schemes and identity
providers (Facebook, Google, OpenID, etc).
Unlike other authentication libraries for use with web applications, a
website using Velruse for authentication does not have to be written in
any particular language.
API
Velruse implements an API similar to RPXNow to standardize the way a
web application handles user authentication.
Velruse Authentication flow
1. Website sends a POST to the auth provider‘s URL with an endpoint that
the user should be redirected back to when authentication is complete
and includes any additional parameters that the auth provider requires.
2. When the auth provider finishes the authentication, the user is
redirected back to the endpoint specified with a POST, which includes
a unique token.
3. Website then makes a query to the UserStore using the token that was
provided. The user’s identity information will be returned, or an
error if the authentication was unsuccessful.
If the website is unable to directly access the UserStore then Step 3 can
be replaced by issuing a HTTP POST in the background to the auth provider
requesting the user’s information with the token.
%package help
Summary: Development documents and examples for velruse
Provides: python3-velruse-doc
%description help
Overview
Velruse aims to simplify authenticating a user. It provides auth
providers that handle authenticating to a variety of identity providers
with multiple authentication schemes (LDAP, SAML, etc.).
Eventually, Velruse will include widgets similar to RPXNow that allow
one to customize a login/registration widget so that a website user can
select a preferred identity provider to use to sign-in.
In the mean-time, effort is focused on increasing the available auth
providers for the commonly used authentication schemes and identity
providers (Facebook, Google, OpenID, etc).
Unlike other authentication libraries for use with web applications, a
website using Velruse for authentication does not have to be written in
any particular language.
API
Velruse implements an API similar to RPXNow to standardize the way a
web application handles user authentication.
Velruse Authentication flow
1. Website sends a POST to the auth provider‘s URL with an endpoint that
the user should be redirected back to when authentication is complete
and includes any additional parameters that the auth provider requires.
2. When the auth provider finishes the authentication, the user is
redirected back to the endpoint specified with a POST, which includes
a unique token.
3. Website then makes a query to the UserStore using the token that was
provided. The user’s identity information will be returned, or an
error if the authentication was unsuccessful.
If the website is unable to directly access the UserStore then Step 3 can
be replaced by issuing a HTTP POST in the background to the auth provider
requesting the user’s information with the token.
%prep
%autosetup -n velruse-1.1.1
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-velruse -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 1.1.1-1
- Package Spec generated
|
