Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / wso2-extensions/identity-outbound-auth-push issues and pull requests
#71 - Use generic names for users in tests
Issue -
State: open - Opened by kushanb almost 4 years ago
#71 - Use generic names for users in tests
Issue -
State: open - Opened by kushanb almost 4 years ago
#70 - Change HTTP response for request from mobile app for authenticating as Accepted
Issue -
State: closed - Opened by kushanb almost 4 years ago
#70 - Change HTTP response for request from mobile app for authenticating as Accepted
Issue -
State: closed - Opened by kushanb almost 4 years ago
#70 - Change HTTP response for request from mobile app for authenticating as Accepted
Issue -
State: closed - Opened by kushanb almost 4 years ago
#70 - Change HTTP response for request from mobile app for authenticating as Accepted
Issue -
State: closed - Opened by kushanb almost 4 years ago
#70 - Change HTTP response for request from mobile app for authenticating as Accepted
Issue -
State: closed - Opened by kushanb almost 4 years ago
#70 - Change HTTP response for request from mobile app for authenticating as Accepted
Issue -
State: closed - Opened by kushanb almost 4 years ago
#70 - Change HTTP response for request from mobile app for authenticating as Accepted
Issue -
State: closed - Opened by kushanb almost 4 years ago
#69 - Implement validations for remove device request from mobile app
Issue -
State: closed - Opened by kushanb almost 4 years ago
#69 - Implement validations for remove device request from mobile app
Issue -
State: closed - Opened by kushanb almost 4 years ago
#69 - Implement validations for remove device request from mobile app
Issue -
State: closed - Opened by kushanb almost 4 years ago
#68 - Change endpoint for remove device API for mobile app use
Issue -
State: closed - Opened by kushanb almost 4 years ago
#68 - Change endpoint for remove device API for mobile app use
Issue -
State: closed - Opened by kushanb almost 4 years ago
#67 - Refactoring and further improvements to push auth servlet component
Pull Request -
State: closed - Opened by kushanb almost 4 years ago
#67 - Refactoring and further improvements to push auth servlet component
Pull Request -
State: closed - Opened by kushanb almost 4 years ago
#67 - Refactoring and further improvements to push auth servlet component
Pull Request -
State: closed - Opened by kushanb almost 4 years ago
#66 - Change SQL queries to refer to push authenticator table
Issue -
State: closed - Opened by kushanb almost 4 years ago
#66 - Change SQL queries to refer to push authenticator table
Issue -
State: closed - Opened by kushanb almost 4 years ago
#66 - Change SQL queries to refer to push authenticator table
Issue -
State: closed - Opened by kushanb almost 4 years ago
#66 - Change SQL queries to refer to push authenticator table
Issue -
State: closed - Opened by kushanb almost 4 years ago
#65 - Use a unique value for getting the list of devices in the device handler
Issue -
State: closed - Opened by kushanb almost 4 years ago
#65 - Use a unique value for getting the list of devices in the device handler
Issue -
State: closed - Opened by kushanb almost 4 years ago
#65 - Use a unique value for getting the list of devices in the device handler
Issue -
State: closed - Opened by kushanb almost 4 years ago
#64 - Refactor Discovery Data method name to be more meaningful
Issue -
State: open - Opened by kushanb almost 4 years ago
#64 - Refactor Discovery Data method name to be more meaningful
Issue -
State: open - Opened by kushanb almost 4 years ago
#63 - Optimise registration flow by changing attributes in QR code and server response
Issue -
State: open - Opened by kushanb almost 4 years ago
#63 - Optimise registration flow by changing attributes in QR code and server response
Issue -
State: open - Opened by kushanb almost 4 years ago
#63 - Optimise registration flow by changing attributes in QR code and server response
Issue -
State: open - Opened by kushanb almost 4 years ago
#63 - Optimise registration flow by changing attributes in QR code and server response
Issue -
State: open - Opened by kushanb almost 4 years ago
#62 - Send a key in push notification by which the auth request message can be processed at device end
Issue -
State: open - Opened by kushanb almost 4 years ago
#62 - Send a key in push notification by which the auth request message can be processed at device end
Issue -
State: open - Opened by kushanb almost 4 years ago
#62 - Send a key in push notification by which the auth request message can be processed at device end
Issue -
State: open - Opened by kushanb almost 4 years ago
#62 - Send a key in push notification by which the auth request message can be processed at device end
Issue -
State: open - Opened by kushanb almost 4 years ago
#62 - Send a key in push notification by which the auth request message can be processed at device end
Issue -
State: open - Opened by kushanb almost 4 years ago
#62 - Send a key in push notification by which the auth request message can be processed at device end
Issue -
State: open - Opened by kushanb almost 4 years ago
#62 - Send a key in push notification by which the auth request message can be processed at device end
Issue -
State: open - Opened by kushanb almost 4 years ago
#61 - Improve authentication flow for instance of selecting one out of multiple registered devices
Issue -
State: open - Opened by kushanb almost 4 years ago
#61 - Improve authentication flow for instance of selecting one out of multiple registered devices
Issue -
State: open - Opened by kushanb almost 4 years ago
#61 - Improve authentication flow for instance of selecting one out of multiple registered devices
Issue -
State: open - Opened by kushanb almost 4 years ago
#61 - Improve authentication flow for instance of selecting one out of multiple registered devices
Issue -
State: open - Opened by kushanb almost 4 years ago
#60 - Refactoring push device handler and further improvements
Pull Request -
State: closed - Opened by kushanb almost 4 years ago
#60 - Refactoring push device handler and further improvements
Pull Request -
State: closed - Opened by kushanb almost 4 years ago
#60 - Refactoring push device handler and further improvements
Pull Request -
State: closed - Opened by kushanb almost 4 years ago
#60 - Refactoring push device handler and further improvements
Pull Request -
State: closed - Opened by kushanb almost 4 years ago
#60 - Refactoring push device handler and further improvements
Pull Request -
State: closed - Opened by kushanb almost 4 years ago
#59 - Refactor push authenticator and further improvements
Pull Request -
State: closed - Opened by kushanb almost 4 years ago
#59 - Refactor push authenticator and further improvements
Pull Request -
State: closed - Opened by kushanb almost 4 years ago
#59 - Refactor push authenticator and further improvements
Pull Request -
State: closed - Opened by kushanb almost 4 years ago
#59 - Refactor push authenticator and further improvements
Pull Request -
State: closed - Opened by kushanb almost 4 years ago
#59 - Refactor push authenticator and further improvements
Pull Request -
State: closed - Opened by kushanb almost 4 years ago
#59 - Refactor push authenticator and further improvements
Pull Request -
State: closed - Opened by kushanb almost 4 years ago
#58 - Push auth authenticator
Pull Request -
State: closed - Opened by kushanb almost 4 years ago
- 1 comment
#58 - Push auth authenticator
Pull Request -
State: closed - Opened by kushanb almost 4 years ago
- 1 comment
#58 - Push auth authenticator
Pull Request -
State: closed - Opened by kushanb almost 4 years ago
- 1 comment
#58 - Push auth authenticator
Pull Request -
State: closed - Opened by kushanb almost 4 years ago
- 1 comment
#58 - Push auth authenticator
Pull Request -
State: closed - Opened by kushanb almost 4 years ago
- 1 comment
#57 - Handle exception for get device API when a device is not found
Issue -
State: closed - Opened by kushanb almost 4 years ago
#57 - Handle exception for get device API when a device is not found
Issue -
State: closed - Opened by kushanb almost 4 years ago
#56 - Handle login attempt when a device isn't registered on IS for push-auth
Issue -
State: closed - Opened by kushanb almost 4 years ago
#56 - Handle login attempt when a device isn't registered on IS for push-auth
Issue -
State: closed - Opened by kushanb almost 4 years ago
#56 - Handle login attempt when a device isn't registered on IS for push-auth
Issue -
State: closed - Opened by kushanb almost 4 years ago
#55 - Update variable names in push-auth device management module in my account according to API changes
Issue -
State: open - Opened by kushanb almost 4 years ago
#55 - Update variable names in push-auth device management module in my account according to API changes
Issue -
State: open - Opened by kushanb almost 4 years ago
#55 - Update variable names in push-auth device management module in my account according to API changes
Issue -
State: open - Opened by kushanb almost 4 years ago
#55 - Update variable names in push-auth device management module in my account according to API changes
Issue -
State: open - Opened by kushanb almost 4 years ago
#55 - Update variable names in push-auth device management module in my account according to API changes
Issue -
State: open - Opened by kushanb almost 4 years ago
#55 - Update variable names in push-auth device management module in my account according to API changes
Issue -
State: open - Opened by kushanb almost 4 years ago
#54 - No persistent layer available for device authentication
Issue -
State: closed - Opened by kushanb almost 4 years ago
#54 - No persistent layer available for device authentication
Issue -
State: closed - Opened by kushanb almost 4 years ago
#54 - No persistent layer available for device authentication
Issue -
State: closed - Opened by kushanb almost 4 years ago
#54 - No persistent layer available for device authentication
Issue -
State: closed - Opened by kushanb almost 4 years ago
#54 - No persistent layer available for device authentication
Issue -
State: closed - Opened by kushanb almost 4 years ago
#54 - No persistent layer available for device authentication
Issue -
State: closed - Opened by kushanb almost 4 years ago
#54 - No persistent layer available for device authentication
Issue -
State: closed - Opened by kushanb almost 4 years ago
#52 - Auth request gets allowed for any response keyword
Issue -
State: closed - Opened by kushanb about 4 years ago
#52 - Auth request gets allowed for any response keyword
Issue -
State: closed - Opened by kushanb about 4 years ago
#52 - Auth request gets allowed for any response keyword
Issue -
State: closed - Opened by kushanb about 4 years ago
#52 - Auth request gets allowed for any response keyword
Issue -
State: closed - Opened by kushanb about 4 years ago
#51 - Update the authentication request payload to support SDK requirements
Issue -
State: closed - Opened by kushanb about 4 years ago
#51 - Update the authentication request payload to support SDK requirements
Issue -
State: closed - Opened by kushanb about 4 years ago
#47 - Parameters duplicated in request to FCM to initiate authentication push message causing a false OK response
Issue -
State: closed - Opened by kushanb about 4 years ago
#47 - Parameters duplicated in request to FCM to initiate authentication push message causing a false OK response
Issue -
State: closed - Opened by kushanb about 4 years ago
#47 - Parameters duplicated in request to FCM to initiate authentication push message causing a false OK response
Issue -
State: closed - Opened by kushanb about 4 years ago
#47 - Parameters duplicated in request to FCM to initiate authentication push message causing a false OK response
Issue -
State: closed - Opened by kushanb about 4 years ago
#46 - Change the key length of the keypair generated for signing challenge text
Issue -
State: closed - Opened by kushanb about 4 years ago
#46 - Change the key length of the keypair generated for signing challenge text
Issue -
State: closed - Opened by kushanb about 4 years ago
#46 - Change the key length of the keypair generated for signing challenge text
Issue -
State: closed - Opened by kushanb about 4 years ago
#43 - Change signing algorithm for mobile authentication
Issue -
State: closed - Opened by kushanb over 4 years ago
#43 - Change signing algorithm for mobile authentication
Issue -
State: closed - Opened by kushanb over 4 years ago
#43 - Change signing algorithm for mobile authentication
Issue -
State: closed - Opened by kushanb over 4 years ago
#43 - Change signing algorithm for mobile authentication
Issue -
State: closed - Opened by kushanb over 4 years ago
#43 - Change signing algorithm for mobile authentication
Issue -
State: closed - Opened by kushanb over 4 years ago
#43 - Change signing algorithm for mobile authentication
Issue -
State: closed - Opened by kushanb over 4 years ago
#41 - Develop WSO2 Verify mobile app using React Native
Issue -
State: open - Opened by kushanb over 4 years ago
- 1 comment
Labels: Severity/Critical, Priority/Highest
#41 - Develop WSO2 Verify mobile app using React Native
Issue -
State: open - Opened by kushanb over 4 years ago
- 1 comment
Labels: Severity/Critical, Priority/Highest
#41 - Develop WSO2 Verify mobile app using React Native
Issue -
State: open - Opened by kushanb over 4 years ago
- 1 comment
Labels: Severity/Critical, Priority/Highest
#41 - Develop WSO2 Verify mobile app using React Native
Issue -
State: open - Opened by kushanb over 4 years ago
- 1 comment
Labels: Severity/Critical, Priority/Highest
#30 - Discuss how "WSO2 Verify" is going to be implemented for iOS
Issue -
State: open - Opened by kushanb over 4 years ago
#30 - Discuss how "WSO2 Verify" is going to be implemented for iOS
Issue -
State: open - Opened by kushanb over 4 years ago