Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 10,000 papers for “Application programming interface”

Метод впровадження багатофакторної аутентифікації в Application Programming Interface

Андрій Олексійович Старосельський · eKNUTSHIR · 2025

Пояснювальна записка до кваліфікаційної роботи «Метод впровадження багатофакторної аутентифікації в Application Programming Interface»: 105 сторінок, 29 рисунків та 1 таблиця. 88 літературних джерел. Актуальність теми: значна кількість успішних кібератак, пов'язаних із компрометацією облікових даних користувачів веб-ресурсів робить традиційні парольні системи недостатньо надійними для сучасних інформаційних систем. Розробка Application Programming Interface (API) з багатофакторною аутентифікацією дозволяє запропонувати рішення цієї проблеми, оскільки додаткові фактори автентифікації суттєво знижують ризик несанкціонованого доступу, особливо враховуючи поширену практику повторного використання скомпрометованих паролів на різних ресурсах. У роботі проведено огляд і аналіз сучасних методів багатофакторної аутентифікації. Розглянуто популярні архітектури API. Досліджено поширені інструменти розробки API. Проаналізовано підходи до впровадження багатофакторної аутентифікації у API. Розроблено метод для впровадження багатофакторної аутентифікації в API. Розглянуті пропозиції щодо практичної реалізації API з багатофакторною аутентифікацією на основі розробленого методу. Мета роботи – розробка методу впровадження багатофакторної аутентифікації у API та його практична реалізація. Об’єкт дослідження – процес аутентифікації користувачів у API. Методи дослідження – методи наукової абстракції, індукції та дедукції (для аналізу та систематизації існуючих підходів до багатофакторної аутентифікації та визначення ключових концепцій); історико-логічний метод (для класифікації та групування існуючих технологій аутентифікації); метод порівняльного аналізу (для оцінки різних підходів до аутентифікації). Наукова новизна: удосконалення методу аутентифікації у API за рахунок впровадження можливості використання багатофакторної аутентифікації.

Cited by 0Open access

Application Programming Interface for Embedded Protocol Management System

Barrera, Mathew David · RIT Scholar Works (Rochester Institute of Technology) · 2024

This paper defines an architecture and software structure which implements a polymorphic system to manage hardware devices. The architecture implements a system to manage integration of hardware devices by providing the constructs required to implement communication and data transport protocols with a method that manages system state independence of each hardware component integrated. The architecture components provide a system which maintains the independence of each device by defining abstractions between each component of the system providing the software constructs required to integrate hardware components which implement differing connections methods and communication protocols. The software architecture provides the means of Integration of multiple systems which do not communicate with the same data representations, states and message passing techniques to build a system that is cohesive and capable of managing reusability and reliability while also defining architectural requirements for the developer which facilitate software cohesion in a volatile software environment. Software roles between components of the system are demarcated to outline the independence of each component of the architecture required to build a system for managing hardware independence while providing state information for each component and preventing contamination between the communication stacks and software application by removing impediments to development in the creation of common interfaces between independent embedded devices. The development life cycle can be shortened by the architecture and protocol management system by defining reusable components able to manage multiple protocols, easing integration and the requirement to develop unique implementations for specific applications and hardware components. The elimination and condensing of differing protocols will remove impediments to development creating common ways to communicate among multiple embedded devices. The implementation of the architecture will aid in the rapid deployment of hardware to an embedded system and will allow for re usability of software modules and lower integration activities by providing a common interface for data producers and consumers, lowering the level of effort required when adding additional hardware components to an embedded system.

Cited by 0

An Application Programming Interface for HighPerformance Distributed Computing

Jahanbakhsh Farahmand Mokarremi, Ashkan Hanif · 2013

This master thesis was performed at Lindahl Lab at Science for Life Laboratory (SciLifeLab), located in Stockholm, Sweden. The need of compute resources is increasing and the speed of a single computer is not enough for data intensive computations. Distributed computing has been developed to improve computations of such tasks by distributing them to other machines. There are many platforms that are implemented for this purpose. Copernicus is such a platform that provides the availability to distribute computationally intensive tasks. The current Copernicus API handles only distribution of entire applications and there is no support to distribute sections of code in Copernicus. In this paper we provide a general API design and a Python implementation of it for how to distribute sections of a code on Copernicus. The implementation of the API handles only Python code but it is possible to extend to other languages with the help of Python wrappers. It also abstracts the learning threshold for a new Copernicus user, especially for those that are not computer scientists or people with little knowledge in programming. Referat API for distribuerade berakningar Detta examensarbete utfordes pa Science for Life Laboratory (SciLifeLab), pa Lindahl Lab avdelning, som ligger i Stockholm. Behovet av datorresurser okar och hastigheten av en enda dator ar inte tillrackligt for dataintensiva berakningar. Distribuerade berakningar har utvecklats for att forbattra berakning av sadana arbeten genom att distribuera dem till andra maskiner. Det finns manga plattformar som har implementerats for detta andamal. Copernicus ar en sadan plattform som ger tillgang till distribuering av berakningsintensiva arbeten. Den nuvarande Copernicus API hanterar endast distribution av ett program i helhet och det finns inget stod for att distribuera delar av kod i Copernicus. I denna rapport tillhandahaller vi ett generellt API-design och dess implementation i Python for hur man distribuerar delar av en kod i Copernicus. Implementationen av APIet hanterar endast Python-kod, men det ar mojligt att utvidga det till andra sprak med hjalp av Python wrappers. Detta minskar aven bort inlarningstroskeln for en ny Copernicus-anvandare, speciellt for dem som inte ar dataloger eller personer med lite kunskap inom programmering.

Cited by 0

Application Programming Interface (API) Security in Cloud Applications

Farhan Qazi · EAI Endorsed Transactions on Cloud Systems · 2023

Many cloud services utilize an API gateway, which enables them to be offered to users through API platforms such as Platform as a Service (PaaS), Software as a service (SaaS), Infrastructure as a Service (IaaS) and cross-platforms APIs. APIs are designed for functionality and speed by developers who write a small portion of code, which has visibility and is secure. The code that is created from third-party software or libraries has no visibility, which makes it insecure. APIs are the most vulnerable points of attack, and many users are not aware of their insecurity. This paper reviews API security in cloud applications and discusses details of API vulnerabilities, existing security tools for API security to mitigate API attacks. The author’s study showed that most users are unaware of API insecurity, organizations lack resources and training to educate users about APIs, and organizations depend on the overall security of the network instead of the security of standalone APIs.

Cited by 13Open access

No-Code Application Programming Interface Testing Platform – Atlas

Emre Torun, Talha Eroğlu, Rıdvan Gülcü et al. · 2025

In today's software-driven world, Application Programming Interfaces (APIs) play a central role in enabling communication between different systems and services. To verify the functionality, reliability, and performance of these interfaces, testing procedures are carried out. Ensuring that API development and testing processes are conducted quickly, efficiently, and accurately is critical for delivering high-quality software services. The complex structure and limited features offered by existing API testing tools often reduces user experience and lead to time loss during the testing process. Moreover, these tools typically store test data on their own servers, posing a potential security risk by exposing sensitive and confidential company data. In this context, a need for a more comprehensive solution for API testing and management processes has emerged. No-code is an innovative approach that requires very little programming experience from the creator of an application, providing great convenience and time savings for developers. The aim of this study is to develop an API testing platform that addresses these needs while maximizing both security and functionality. To achieve this, a no-code API test platform called "Atlas" has been developed. The platform has been designed as a desktop solution using Electron, with the user interface builted in React. The back end utilized Node.js for automatic updates and version control, and Couchbase has been selected as the database. The platform provided a customizable framework that aligned with corporate requirements and demonstrated the effectiveness of creating codeless API testing. With the developed platform, it has reduced both cost and security-related risks.

Cited by 0

Google Drive forensic analysis via application programming interface.

Shujian Yang · SHAREOK (University of Oklahoma) · 2020

Rapid development of cloud computing brings challenges to digital forensic investigation, where traditional digital forensic tools and methodologies do not apply well. New approaches are needed to overcome emerged problems. This research focuses on analyzing a popular cloud storage service Google Drive in a forensically sound manner. The application programming interface (API) approach is chosen as the main method to perform digital forensic investigation. A sample application is developed to acquire evidence from Google Drive. Experiments were then conducted to evaluate its effect based on results. By comparing the results with other approaches, the API approach proves to be effective and reliable for digital forensic examiners and forensic software developers to consider as available tool in their arsenal.

Cited by 0

Pembuatan Aplikasi Lelang Berbasis Application Programming Interface Facebook

Chandra, Willy · Ubaya Repository (University of Surabaya) · 2011

Setiap orang memiliki kebutuhan sehari-hari dalam hidupnya. Untuk memenuhi kebutuhan tersebut setiap orang melakukan transaksi. Contohnya seorang ibu rumah tangga yang pergi ke pasar untuk memenuhi kebutuhan pangan keluarganya. Pada umumya transaksi diawali pencarian informasi barang, pencarian barang alternatif, pencarian tempat penjualan, perbandingan harga, dan pembayaran. Segala tahap proses mulai dari pencarian informasi hingga pembayaran tentunya membutuhkan waktu dan biaya bila menggunakan cara konvensional. Diperlukan waktu dan biaya untuk melakukan pencarian informasi. Begitu pula pada saat menuju tempat penjualan barang. Saat sampai di tempat penjualan bila harga barang tidak sesuai atau habis maka pembeli harus kembali pada tahap pencarian informasi. Adanya permasalahan tersebut mendasari pembuatan aplikasi lelang online berbasis Facebook API. Penggunaan sistem lelang dimaksudkan agar harga lebih kompetitif dan menguntungkan bagi penjual ataupun pembeli sedangkan, Facebook memiliki sebuah jaringan network yang luas sehingga penyebaran informasi lebih cepat dan luas. Proses terkomputerisasi secara online memungkinkan pencarian yang cepat dan luas terhadap suatu barang kebutuhan. Biaya koneksi internet yang semakin murah turut menekan proses transaksi online. Agar aplikasi yang dibuat dapat membantu secara efektif bagi pembeli maupun penjual maka dalam pembuatan aplikasi ini akan dilakukan dahulu analisis terhadap sistem yang sedang berjalan saat ini. Lalu berdasarkan hasil analisis dilakukan desain sistem, perencanaan, dan implementasi sistem. Setelah implementasi selesai, dilakukan uji coba terhadap sistem yang terjadi dari dua tahap, verifikasi dan validasi. Dari hasil verifikasi dan validasi tersebut dapat disimpulkan bahwa aplikasi yang dibuat mampu membantu proses transaksi menjadi lebih singkat dan murah. Kesimpulan dari pembuatan aplikasi lelang berbasis Facebook API ini adalah bahwa aplikasi lelang ini dapat digunakan penjual dan pembeli untuk menekan biaya serta mempercepat proses transaksi. Aplikasi lelang ini juga dapat menyimpan data-data transaksi yang telah terjadi sehingga dapat digunakan bila sewaktu-waktu terjadi masalah Saran yang diusulkan adalah agar ditambahkan suatu sistem pembayaran khusus untuk meningkatkan keamanan transaksi. Pembuatan forum sebagai media tanya jawab tentang informasi suatu barang.

Cited by 0Open access

API Application Programming Interface BAR Backbone Access Router

Mark Leese, Robin Tasker, Cclrc Council et al. · 2008

At last year’s inaugural AllHands meeting, our paper outlined the proposed development of a comprehensive and extensible network monitoring infrastructure for UK e-Science. This paper initially serves as an update, outlining the last year’s good progress in establishing an infrastructure which is already supplying tangible benefits. The paper then introduces the project’s second phase, which will see GridMon’s integration into Grid technology via compliance with the Open Grid Services Architecture. The starting point for this journey has been the development of GridMon as a web service. This, and future stages of the journey will be outlined. GridMon is not alone in developing a network monitoring system as a web and/or Grid service. Also described, as part of GridMon’s aim to be a “best of breed ” network monitoring system for UK e-Science, are ongoing collaborations such as those with the Internet2 piPEs initiative. Finally, consideration is given to new work which seeks to redress some of the widely observed imbalance between the achieved and expected network performance of end users. By building on relevant research, GridMon hopes to provide “best practice ” examples of TCP configuration, with our monitoring results showing these in a real world rather than ‘laboratory ’ context. Glossary:

Cited by 0

ePAPI: Performance Application Programming Interface for Embedded Platforms

Jeremy Giesen, Enrico Mezzetti, Jaume Abella et al. · DROPS (Schloss Dagstuhl – Leibniz Center for Informatics) · 2019

Performance Monitoring Counters (PMCs) have been traditionally used in the mainstream computing domain to perform debugging and optimization of software performance. PMCs are increasingly considered in embedded time-critical domains to collect in-depth information, e.g. cache misses and memory accesses, of software execution time on complex multicore platforms. In main-stream platforms, standardized specifications and applications like the Performance Application Programming Interface (PAPI) and perf have been proposed to deal with variable PMC support across platforms, by providing a shared interface for configuring and collecting traceable events. However, no equivalent solution exists for embedded critical processors for which the user is required to deal with low-level, platform-specific, and error-prone manipulation of PMC registers. In this paper, we address the need for a standardized PMC interface in the embedded domain, especially in view to support timing characterization of embedded platforms. We assess the compatibility of the PAPI interface with the PMC support available on the AURIX TC297, a reference automotive platform, and we implement and validate ePAPI, the first functionally-equivalent and low-overhead implementation of PAPI for the considered embedded platform.

Cited by 2Open access

Usability analysis of the channel application programming interface

Christopher Brown · Calhoun: The Naval Postgraduate School Institutional Archive (Naval Postgraduate School) · 2003

The Channel Application Programming Interface (API) provides a tool for loosely coupling components in Component Based Design (CBD) projects In the thesis that proposed and developed the API, the author provided a technical analysis of the API's performance with respect to communication metrics However, only the author/designer has ever used the API; hence, no analysis was accomplished with respect to usability attributes, The project sponsor desires public release of the API, especially within the Department of Defense (DoD) However, a usability analysis is first required to ensure wide acceptance and use of the API, In order to analyze the API, an analysis method and associated metrics are required, Little work has been done in the field of Human Computer Interface (HCI) with respect to treating an API as an interface and programmers as the end users, This thesis follows an IEEE published case-study and well known HCI usability analysis methods to test the API for general usability attributes as well as to investigate specific features of the API, Specifically, the analysis will test the API's ability to explain its functionality during first time exposure, The API's acceptance will depend on its success or failure to convey its purpose quickly during this initial exposure, The results from testing the API are used to determine required enhancements to the API and its documentation.

Cited by 2Open access

Synchronization-free multithreading architecture and application programming interface

Haitham Akkary, Sami Ramly, Karim Serhan · 2014

We present a multithreading architecture and application programming interface (API) for writing and executing synchronization-free shared-memory parallel applications. The API provides simple directives with which a programmer can specify parallel or mostly parallel threads in a C/C++ program. In case of inter-thread data dependences, the programmer simply declares these dependences instead of using synchronization directives that serialize the dependent threads execution. The hardware uses the dependences declared by the programmer to split the program execution into disjoint control and data threads that execute concurrently on multiple cooperating latency-tolerant out-of-order cores. We show that the new architecture with its API allows a programmer to parallelize code that is otherwise non-parallelizable with existing parallel programming APIs, such as OpenMP, thus providing better programmability and higher performance. We use as an example Viterbi algorithm code to explain the new architecture and its API and a multicore performance simulator to highlight its performance potential.

Cited by 1

Supporting Simultaneous Multiaccess in IPv6 Application Programming Interface

Ylitalo, Jukka · Aaltodoc (Aalto University) · 2020

Nykyinen kehityssuunta on kohti monioperaattoriympäristöä, jossa päätelaite ei ole kytkeytynyt enää vain yhteen access verkkoon. \nSen sijaan liikkuva päätelaite, jolla on useita rajapintoja, voi kytkeytyä useisiin access verkkoihin samanaikaisesti. \nVerkot voivat kuulua eri operaattoreille ja verkkoteknologiat voivat vaihdella esimerkiksi ethernet verkoista GPRS verkkoihin. \n\nUudet protokollat mahdollistavat samaan liikennöintivirtaan kuuluvien pakettien dynaamisen jakamisen eri access verkkojen välillä. \nMenetelmää kutsutaan myös rinnakkaiseksi verkkoyhteydeksi. \nProtokollakuvaukset eivät kuitenkaan määrittele ohjelmointirajapintaa rinnakkaisille verkkoyhteyksille. \n\nTyössä on analysoitu olemassa olevia IPv6 ohjelmointirajapintoja ja rinnakkaisia verkkoyhteyksiä tukevia protokollia. \nAnalyysin perusteella on suunniteltu ja toteutettu ohjelmointirajapinta rinnakkaisille verkkoyhteyksille. \nOhjelmointirajapinta on suunniteltu käytettäväksi Homeless Mobile IPv6 protokollan kanssa, mutta soveltuu yleisesti myös muille rinnakkaisia verkkoyhteyksiä tukeville protokollille.

Cited by 0

System Memory Monitoring through windows application programming interface

A. Noraziah, A.S. Hafizulrahim, Ramli Muhammed Ramiza et al. · 2008

System Memory Monitoring (SMM) has been developed to observe the current process usage and memory usage in Windows operating system in term to handle the problem that might be occurs such virus, spyware and the failure process that using abnormal usage. Currently available application such Window Task Manger has the weakness, which the running process does not provides detail information like process size, location path, product name and etc. Therefore, SMM is developed to enhance this application, while at the same provides an additional feature such as a graph flow to make the user more understand the computerpsilas memory flow. Windows Application Programming Interface (API) is used by SMM as the fundamental resources in Windows operating system. As a result, SMM able to recognize the running process by providing details information.

Cited by 1

A Proposed Application Programming Interface for a Physical

Volume Repository Merritt, Merritt Jones · 1996

This document, dated September 8, 1994, provides the framework for a series of standards for application and user interfaces to open storage systems. More recently, the SSSWG has been developing Application Programming Interfaces (APIs) for the individual components defined by the model. The API for the Physical Volume Repository is the most fully developed, but work is being done on APIs for the Physical Volume Library and for the Mover also. The SSSWG meets every other month, and meetings are open to all interested parties. Further information on the SSSWG may be found at http://www.arl.mil/IEEE/ssswg.html

Cited by 0