You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Release notes - Verity 2.8.0 (0.4.110434998.b502641) - Jan 13 2021
Bugs
* [VE-2281] - Not possible to provision a token in .NET SDK
Tasks
* [VE-2017] - Define Messages for BasicMesasge (Control, Signal, Protocol)
* [VE-2018] - Implement Protocol Logic for BasicMessage
* [VE-2019] - Implement Integration tests for BasicMessage
* [VE-2020] - Wire new Protocol for BasicMessage
* [VE-2021] - Implement BasicMessage protocol in Verity-SDK (java, python, node, .NET)
* [VE-2022] - Add required documentation for Basic Message
* [VE-2046] - Expose LibIndy instrumentation as custom metrics in Verity
* [VE-2138] - Add connection-reuse flow for OOB with request attach
* [VE-2249] - Catch up .NET SDK with the other SDKs (add Propose proof and names restriction changes)
* [VE-2287] - Write Schema and Write CredDef should support "endorsing flow"
Release notes - Verity 2.7.0 (0.4.107364822.a2523bb) - Dec 9 2020
Bugs
* [VE-2133] - Verity does not return attribute values in presentation-result if names syntax is used
Tasks
* [VE-2010] - Add integration test for proposed presentation to verity
* [VE-2220] - Create public Dockerhub image for Verity sample app
* [VE-2244] - Provision Token delivered via push notification and HTTP response
Release notes - Verity 2.6.0 (0.4.105917705.a19f4a0) - Nov 25 2020
Tasks
* [VE-2008] - Add protocol messages for proposed presentation to verity
* [VE-2009] - Add protocol logic for proposed presentation to verity
* [VE-2011] - Add required APIs to verity-sdk
* [VE-2093] - Added OOB with request-attach to Integration Tests
* [VE-2096] - Document new API - OOB with request attach
* [VE-2116] - Update getting started guides for .NET SDK
* [VE-2117] - Making environment for build and publication on the NuGet
* [VE-2120] - Update Verity SDK CI/CD pipelines for .NET
* [VE-2124] - Remove 0.6 Provisioning Protocol
* [VE-2125] - Return provision token in http response if NOT push notification format
Release notes - Verity 2.5.0 (0.4.103141332.ef1e3e6) - Oct 21 2020
Bugs
* [VE-1968] - Python SDK example app sometimes throws libindy warning
* [VE-1997] - If label is not specified in Relationship create call, Python and Java SDKs do not default to the label specified in UpdateConfigs
* [VE-2015] - UPDATE_CONFIG protocol setting the logoUrl to null generates a NullPointerException and then crashes the UserAgent actor
* [VE-2057] - Not possible to specify the walletPath in public constructors for NodeJS SDK
Stories
* [VE-1564] - Validation of SMS phone number format
* [VE-1779] - Create Sample Web App demoing Connection-reuse
* [VE-1974] - Cannot specify self attested values during Prover's Interaction in Present Proof
* [VE-1976] - Trust-ping response can not be mapped to relationshipDID which sent the ping
* [VE-1990] - publicDid missing in case of SMS connection redirect for old (0.5 and 0.6 protocols)
Stories
* [VE-1528] - As Evernym Verity Customer, I want to send Connection invites v1.0 using SMS to Connect.Me
* [VE-1966] - Verification result "ProofUndefined" in presentation-result message
* [VE-1969] - Add threadId() for WriteSchema protocol in all 3 SDKs
* [VE-1970] - Problem with push notifications with Aries protocols
Stories
* [VE-1967] - When protocol receives unexpected message (for state) it should respond with problem-report.
* [VE-1975] - Add message type to outer layer of aires outgoing messages
* [VE-1977] - Short URL returns c_i in the response body
* [VE-1957] - No linkage between relationship-reused thid/pthid and OutofBand invitation message thid/@id
* [VE-1958] - profileUrl is not set when out-of-band-invitation is used
Stories
* [VE-1491] - As Evernym Customer using Aries 1.0 connections protocol, I need to have be able to send a connection using URL
* [VE-1811] - Verity Application needs to persists events in docker container
* [VE-1883] - Implement support for goal-code and goal in Out-Of-Band protocol on Verity
* [VE-1925] - Fix legacy agent routes (found issues during release)
* [VE-1926] - relationship data model validation issues
Release notes - Verity 2.2.0 (0.4.98263760.043e6b5) - Aug 26 2020
Bugs
* [VE-1667] - Field verification_result in presentation-result message has a wrong value
* [VE-1829] - Question answer should use url_safe base64 encoding.
* [VE-1899] - Example app crashes when Verity Application endpoint with trailing slash is specified
* [VE-1900] - Fix example app output once if expired token is used.
Stories
* [VE-1551] - Cache used provisioning tokes on Verity so token cannot be used more than once within the token window
* [VE-1790] - Publish verity intergration test runner
Release notes - Verity 2.1 (0.4.95258837.49f840f) - July 28 2020
Bugs
* [VE-1457] - Node.Js Verity SDK bug with uuid dependency
* [VE-1542] - Committed Answer protocol not working on the Verity 2.0 (0.4.91738644.3fe8dde)
* [VE-1559] - Acme Corp (try.connect.me) should be using proper logo instead of the robohash logo
* [VE-1581] - Verity should be using Enterprise name and logo from the UpdateConfigs call in the ConnectionInvitation
* [VE-1605] - DynamoDB high read condition
* [VE-1659] - Endpoint URLs containing IP addresses fail URL validation
* [VE-1667] - Field verification_result in presentation-result message has a wrong value
* [VE-1637] - Faber/Alice demo broken on team1 EAS
* [VE-1500] - Fix problem with too much logging in CAS
Tasks
* [VE-1540] - As Evernym TE, I need to add puppet config for enforcing token provisioning on VAS
* [VE-1554] - Change REST API token provisioing script to use 0.7
Stories
* [VE-1322] - As Verity customer, I want to be able to issue credential in one step (instead of two)
* [VE-1412] - Create comprehensive Verity SDK documentation
* [VE-1458] - Design and Implement connection redirect (or connection reuse) on Verity using Aries protocols
* [VE-1536] - Log wrongly formatted REST API payload
* [VE-1547] - As Evernym Customer, I want access a source code of web app based on vcx-customer toolkit
* [VE-1557] - As Evernym Verity SDK customer, I want to install Verity SDK from language specific repos
* [VE-1568] - As Evernym Verity SDK customer, I want a way to easily run example apps using Docker
* [VE-1621] - I want to configure a custom SMS text message per customer
* [VE-1590] - Add support for multiple sponser app to be able to use push notification service
* [VE-1672] - Tokenizer use sponsor push service
Release Notes - Verity version 2.0 (0.4.91738644.3fe8dde) - Jun 17 2020
Bugs
* [VE-1395] - Fix memory leaks issues
* [VE-1444] - indy-sdk logging--should explicitly set logging to INFO not TRACE
Stories
Multi-tenancy
* [VE-1147] - As Evernym, we can provision multiple customers (Issuer Identities or tenants) to one Verity server instance
* [VE-1121] - As Verity SDK customer, I'm able to register (perform) provisioning of multiple SDK instances to my one Verity Server so I can have multiple client codes using one Verity Server
* [VE-1316] - As Verity REST customer, I'm able to register more than one REST client to Verity instance
* [VE-1148] - As Evernym, we need to be able to differentiate different tenants on one Verity Server (Customer Identifier)
Aries
* [VE-1538] - Implement Trust Ping AIP v1 protocol on Verity
* [VE-1378] - Implement REST API for Aries protocols
Other
* [VE-1381] - Improve Verity SDK documentation
* [VE-1409] - Update UPDATE_COM_METHOD protocol
* [VE-1504] - REST json responses from http endpoint should have content-type set to application/json instead of text/plain
* [VE-1490] - As Evernym, I need to update Acme corp of try.connect.me to use Aries (1.0) protocols and new SDK
Release Notes - Verity version 1.8 (0.4.88971934.01eadf6) - May 11 2020
Bugs
* [VE-1382] - Public DID in the Connection Invite is wrong one for both SDK and REST API
* [VE-1390] - Connection get status missing sourceId
Stories
Aries
* [VE-1066] - Implement Aries protocols for connecting/issuing/proving in Verity
REST API
* [VE-1151] - Issuer setup REST API
* [VE-1153] - Create Schema REST API
* [VE-1154] - Create cred def REST API
* [VE-1155] - Connection establishment (DID exchange) REST API
* [VE-1156] - Issue credential REST API
* [VE-1157] - Request and validate proof REST API
* [VE-1158] - Send and receive Committed Answer REST API
* [VE-1159] - Retrieve Connection Invite protocol status REST API
* [VE-1161] - Retrieve Request and validate proof protocol status REST API
* [VE-1162] - Retrieve Send and receive Committed Answer protocol status REST API
* [VE-1326] - Organization name&logo REST API
* [VE-1327] - Configure Webhook REST API call
* [VE-1357] - Create OpenAPI (formerly know as swagger) documentation for REST API
* [VE-1363] - Implement throttling on REST API endpoints on Verity
* [VE-1386] - Create python script for provisioning API keys for REST API
Verity SDK
* [VE-1403] - Add a method for creating REST API key for existing Verity SDK users
* [VE-1406] - Update Getting Started with Verity SDK
Other
* [VE-1402] - Add resource usage block on the PROVISION protocol
* [VE-1418] - Add msg response time related 'span' metrics for all protocol messages
* [VE-1364] - Metrics (latency and response times) on Verity REST endpoints