Found 64 packages
An implementation of TOTP and HOTP which are commonly used for multi factor authentication by using a shared key between the client and the server to generate and verify one time use codes. For documentation and examples visit the project website on GitHub at https://github.com/kspearrin/Otp.NET
.Net library for two-factor (or multi-factor) authentication using TOTP and QR-codes.
This is an implementation of HOTP and TOTP which are commonly used for multi factor authentication by using a shared key between the client and the server to generate and verify one time use codes. This library is capable of generating and verifying both TOTP and HOTP authentication codes. The calculations in this library are known to be compatible with Google 2-Step Verification and consequently the Google Authenticator smartphone app. It is also known to be able to generate codes for Amazon Web Services Multi Factor Authentication and Dropbox 2 step authentication. It should work with any other service or client that is RFC compliant. This library is released under an MIT license. No warranty is provided as to the correctness of the library and the consumer of the library assumes all risk for the use thereof, as per the MIT license. Every effort has gone into implementing this library in accordance with the RFCs mentioned above. However it is up to the users of this library to read through the RFCs and ensure that this implementation is in accordance with the security procedures outlined therein. The implementation includes the code calculation as well as simple verification. Persistence of the keys, secure key storage, ensuring that a single code can't be validated multiple times and other things are not a part of this library. Thus far those functions (and any others mentioned in the RFCs) are up to the consumer of this library. For documentation please visit the project website.
Boot.Multitenancy v.1.6.5 Multitenancy is a NHibernate (ISession) helper for ISessionFactory. Support multiple domains and databases in a single instance. Contains a lot of extensions. Consult project website for more information.
support multi session factory and mvc3.
Bonyan Modularity Framework v1.6.0 - A microkernel architecture framework for building modular .NET applications. Version 1.6.0 Changes: • Breaking: Introduced phase-specific configuration contexts (BonPreConfigurationContext, BonConfigurationContext, BonPostConfigurationContext) for stricter architectural control • Breaking: Removed [DependsOn] attribute support - all modules must use constructor-based dependency declaration (DependOn<TModule>()) • Enhanced: Recursive module discovery starting from root entry point with improved dependency graph visualization • Fixed: LoggerFactory disposal issues, IBonUnitOfWorkManager resolution, and module lifecycle management • Improved: Better separation of concerns between presentation/infrastructure and domain layers See RELEASE_NOTES.md for complete migration guide and detailed changelog.
MultiPlug CFX Extension for the Connected Factory Exchange. Based on the IPC-2591 AMQP 1.0 Standard. Use this extension to push MultiPlug Events to a CFX broker.
Fork of the Microsoft.Data.Sqlite project that adds .NET Framework 4.0 support for multi-targeted libraries. SQLite implementation of the System.Data.Common provider model. Commonly Used Types: Microsoft.Data.Sqlite.SqliteCommand Microsoft.Data.Sqlite.SqliteConnection Microsoft.Data.Sqlite.SqliteConnectionStringBuilder Microsoft.Data.Sqlite.SqliteDataReader Microsoft.Data.Sqlite.SqliteException Microsoft.Data.Sqlite.SqliteFactory Microsoft.Data.Sqlite.SqliteParameter Microsoft.Data.Sqlite.SqliteTransaction
Fork of Sdl.MultiSelectComboBox with .Net 4.6 support. Removed item grouping feature as it is not supported in .Net 4.6. I also added the ability to create selection items on the fly (see EnableNewItemsCreation and ItemFactoryService) properties
A UiPath custom activity that generates Time-based One-Time Passwords (TOTP) using a secure secret key. Supports Base32 encoding and String input for enhanced security. This activity is useful for two-factor authentication (2FA) workflows.
Cloudmersive Virus Scan API Client for .NET Core allows you to scan files, URLs, and webistes for viruses, malware, trojans, ransomware, spyware, and many other types of threats. Multi-factor scanning across many delivery methods including polymorphic and multipartite. Scanning supports files, archives, and recursive file formats.
Shortcuts for adding TOTP multi-factor authentication support to HealtCheck login.
Shortcuts for adding FIDO2/WebAuthn multi-factor authentication support to HealtCheck login.
With EFCore.DbContextFactory you can resolve easily your DbContext dependencies in a safe way injecting a factory instead of an instance itself, enabling you to work in multi-thread contexts with Entity Framework Core or just work safest with DbContext following the Microsoft recommendations about the DbContext lifetime.
Cloudmersive Virus Scan allows you to scan files, URLs, and webistes for viruses, malware, trojans, ransomware, spyware, and many other types of threats. Multi-factor scanning across many delivery methods including polymorphic and multipartite. Scanning supports files, archives, and recursive file formats.
A C# .NET 9.0 Blazor library enabling simple passkey authentication.
This logging library makes large use of enterprise correlation. In a lot of applications that incorporate various small and large services, it is often important to correlate events that happen across these services. It gives us a business workflow view of the various events that happen in the application, its components and services. This library provide operation and activity ID management and propagation. The main difference with this library over other is that you can configure each type of log separately. You can enable fatal, error, warning, debugging, informational, progress and sensitive data logging all independently of each other. This is more flexible than the concept of minimum level logging, such as that in log4net or serilog e.g. enabling one warning in this libraries will enable error and fatal logging as well. This library allows you to set those settings independently of each other. The SqlLogger maps AdditionalData to table columns, where the key of the dictionary entry is the column name and the value is serialised to JSON as the column value. MetaData is serialised to a single JSON value stored in the MetaData column. This means you can store data such as a User ID or Job ID in a separate column so you can filter more efficiently with indexes and partitions. TraceLogger and ConsoleLogger both seralise and format all information into a single string. The MultiLogger allows you to configure several different loggers to be used at once with different settings for each logger. Usage is in the form of: static void Main() { ICorrelationIdHelper correlationIdHelper = new WebCorrelationIdHelper(); // This value will be set automatically to all logs within this thread... so long as System.Threading.Tasks.Task.Factory.StartNew is used. correlationIdHelper.SetCorrelationId(Guid.NewGuid()); DoSyncWork(); DoAsyncWork(); } static void DoSyncWork() { ILogger logger = new SqlLogger(); logger.LogDebug("Some technical debugging details."); } static void DoAsyncWork() { System.Threading.Tasks.Task.Factory.StartNew(() => { ILogger logger = new ConsoleLogger(); logger.LogInfo("An informative message."); }); } This package installs cdmdotnet.Logging.dll with includes core logging functionality. Other packages depend on cdmdotnet.Logging for specific implementations.
Cipherise does away with passwords and usernames, giving your customers an easy, secure login with their mobile device. With a simple, quick scan of a WaveCode, they can achieve multi-factor authentication in a single action. * Move towards a passwordless experience for your customers. * No more complicated passwords and usernames. * A simple, fast experience that is consistent across multiple services. * No more credential sharing. By design Cipherise decentralises critical information (identity, credentials and critical data). Each user's credentials are encrypted and stored in a secure enclave on their personal device. The credentials are never stored elsewhere or transmitted through a browser. This protects your customers' data and digital identity. * All Cipherise authentication transactions are decentralised and completed on a user's mobile phone. * Credentials are stored locally on the user's phone in encrypted form, not centrally with the service provider. * Credentials are never transmitted or stored outside of the user's phone.