How to Install and Uninstall python310-flask-jwt-extended Package on openSuSE Tumbleweed

Last updated: November 24,2024

1. Install "python310-flask-jwt-extended" package

Please follow the guidelines below to install python310-flask-jwt-extended on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                python310-flask-jwt-extended
            
                    
    
    Copied

2. Uninstall "python310-flask-jwt-extended" package

In this section, we are going to explain the necessary steps to uninstall python310-flask-jwt-extended on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                python310-flask-jwt-extended
            
                    
    
    Copied

3. Information about the python310-flask-jwt-extended package on openSuSE Tumbleweed

Information for package python310-flask-jwt-extended:
-----------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python310-flask-jwt-extended
Version : 4.6.0-1.2
Arch : noarch
Vendor : openSUSE
Installed Size : 159.3 KiB
Installed : No
Status : not installed
Source package : python-flask-jwt-extended-4.6.0-1.2.src
Upstream URL : https://github.com/vimalloc/flask-jwt-extended
Summary : A Flask extension that provides JWT support
Description :
Flask-JWT-Extended not only adds support for using JSON Web Tokens
(JWT) to Flask for protecting views, but also many
(optional) features built in to make working with JSON
Web Tokens easier. These include:
- Support for adding custom claims to JSON Web Tokens
- Custom claims validation on received tokens
- Creating tokens from complex objects or complex object from received tokens
- Refresh tokens
- Token freshness and separate view decorators to only allow fresh tokens
- Token revoking/blacklisting
- Storing tokens in cookies and CSRF protection