I am trying to configure Net-SNMP to accept incoming SNMP v3 requests at proxy agent and forward the requests to other internal application servers.
I have investigated and read tons of comments but I could not find how to query the proxy agent with SNMP v3 and enforce proxy agent to parse and forward this query as SNMP v2c request.
Your assistance would be highly appreciated. Thanks a lot
Related
I have an use case where I have services which require interaction with DynamoDB (Programming env is in golang). But assume these service doesn't have AWS credentials and I have custom AuthN/AuthZ mechanism to validate the services internally and set credentials. So, I want to write a AuthN proxy service which intercepts requests to DynamoDB, check what type of operation (Get/Set/Delete), validate them, set DDB credentials to that request, query dynamodb and send response back to clients. I tried using proxy as mentioned here in DDB documentation, but it is HTTP Connect tunnelling and I couldn't intercept traffic in between as it is HTTPS traffic to DynamoDB. Can someone tell me how I can achieve this using AWS Go sdk library?
Thanks in advance.
Previously I configured api/services on Kong as HTTP and it was working fine. Now I made api/services as HTTPS in back end and I changed protocol http to https for all api/services on Kong. But after changing http to https protocol i unable to access api's.
Can you please tell me what I have to do?
Here is my services configuration on kong
Route
Please help me.
HTTPS is used to protect data exchanges from anyone looking into them.
You are configuring data exchange between your gateway and upstream servers.
Your microservices are most likely deployed into the same closed virtual private network where kong gateway is located.
It is unlikely that anyone could sniff on data traffic which goes between API gateway and your microservices.
Setup of encryption in your virtual private network will just waste computational resources which you could allocate to extra workers which do usefull things.
What you probably need is to configure SSL certificate at kong gateway public interface.
To do this you can add your SSL certificate in Konga GUI in CERTIFICATES section.
I am new to SNMP agent implementation. A confusion regarding the usage of SNMP4J API is, which SNMP4J Api should be used to create the agent? Should it be SNMP4J or SNMP4J-Agent?
An agent is some kind of server: it mainly replies to requests (it may occasionally also send traps to managers).
A manager is a some kind of client: it mainly send requests to agents (it may occasionally also receive traps from managers).
SNMP4J is the library for managers to send requests to remote agents.
SNMP4J-Agent is the library for agents to reply to requests.
So, to write a SNMP agent, you need to use SNMP4J-Agent jar file.
The task is to build SMTP proxy gateway which will send all letters to API for some checks and dependently of API answer will send letter to destination server or will return error message to client.
Please look at this picture
IMAP will be organized in same way, all letters will be sent to API for virus checking etc. and only letters with successfull API response will be received to mailbox.
Want to ask and advice which software will be better to use for this purpose. Dovecot/Postfix? But how to integrate it with AMQP API? Maybe better will be to organize it through nginx proxy? Or python Twisted framework?
Will be grateful for any help.
If you're looking for a COTS software solution, Forum Sentry API Security Gateway software version can act both as an SMTP proxy or an AMQP proxy.
http://www.forumsys.com/forum-sentry-secure-amqp-proxy/
[I work for Forum Systems]
I need to connect to Exchange Server in Mule but Mule provided OOB IMAP and POP3 are not enabled on our exchange server hence we cannot use them.
Can anyone shed some light here on other alternative ways to connect to exchange server and read the emails.
Mule mail transport implements standard transports, these being IMAP, POP3 and SMTP.
If you need anything beside these to access your mail server you should consider writing a custom connector using devkit.
An example of such an approach is the gmail connector that leverages google API to retrieve emails rather than the standard mail transport.
Most of the connections from the Internet are handled by IIS on the Exchange Server. The options can be:
RPC Over Https. Well known as “Outlook Anywhere”.
EWS. Mostly used by MAC Outlook.
Activesync – Mobility
ECP – management console, configuration via OWA
Thanks,
hope answer the question